Xref: utzoo comp.sources.d:2026 comp.binaries.ibm.pc.d:110
Path: utzoo!mnetor!uunet!mcvax!ukc!warwick!cudcv
From: cudcv@daisy.warwick.ac.uk (Rob McMahon)
Newsgroups: comp.sources.d,comp.binaries.ibm.pc.d
Subject: Re: Standard for file transmission
Message-ID: <537@sol.warwick.ac.uk>
Date: 4 May 88 19:01:58 GMT
References: <292@cullsj.UUCP>
Reply-To: cudcv@cu.warwick.ac.uk (Rob McMahon)
Organization: Computing Services, Warwick University, UK
Lines: 21
Keywords: protocol compression source

In article <292@cullsj.UUCP> jeff@cullsj.UUCP (Jeffrey C. Fried) writes:
>The following tools are 
>available in source code format:  COMPRESS (Lem-Ziv text compressor), ARITH
>(arithmetic compression for binary), UUencode/decode.  Since all of these
>will run under a variety of environments (IBM-PC, AMIGA, ATARI, VMS, SYS5,
>BSD), why not make these the basis for communicating.

I hope we're talking about binary files here, in which case I don't care
because I'd never just take a binary from the net and run it on one of my
machines.  If you're talking about sources, I like to scan down, read the
README, check out the comments in main etc., before I even save it to disk.
If I get all the bits of a posting, tack them together, uudecode them, and
uncompress them, only to find it's of no use to me, I'm not going to be
amused.  I have this feeling that people aren't going to bother to send proper
introductory articles in plain text before the actual posting.

Rob
-- 
UUCP:   ...!mcvax!ukc!warwick!cudcv	PHONE:  +44 203 523037
JANET:  cudcv@uk.ac.warwick.cu          ARPA:   cudcv@cu.warwick.ac.uk
Rob McMahon, Computing Services, Warwick University, Coventry CV4 7AL, England