Path: utzoo!utgpu!cs.utexas.edu!sdd.hp.com!ucsd!network.ucsd.edu!slamont
From: slamont@network.ucsd.edu (Steve Lamont)
Newsgroups: alt.sources.d
Subject: compressed postings (was Re: Read this if you're having trouble unpacking Tcl)
Message-ID: <4418@network.ucsd.edu>
Date: 30 Dec 90 18:52:18 GMT
References: <1990Dec28.075123.6114@zorch.SF-Bay.ORG> <4044@dah.sub.org> <1990Dec30.151724.20808@zorch.SF-Bay.ORG>
Distribution: alt
Organization: Naval Postgraduate School, Monterey, CA
Lines: 23

In article <1990Dec30.151724.20808@zorch.SF-Bay.ORG> xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes:
>Filesystem            kbytes    used   avail capacity  Mounted on
>/dev/gd4f             231133   99129  108890    48%    /usr/spool/news
>
>231Mbyte spool file; replicate that 20 or so times with other source
>group postings, and you're talking a day saved for expires. I'd like that.

It seems that what the discussion *should* center around is more efficient
file transport and/or storage methods, not whether the postings themselves
should be compressed/encoded/whatevered.  All of this compression/
decompression and so forth should be invisible to the ultimate
reader/user.  Making the individual reader go through this process is very
user unfriendly.

							spl (the p stands for
							pardon me, can I
							compress a word in
							edgewise?)
-- 
Steve Lamont, SciViGuy -- 1882p@cc.nps.navy.mil -- a guest on network.ucsd.edu
NPS Confuser Center / Code 51 / Naval Postgraduate School / Monterey, CA 93943
What is truth and what is fable, where is Ruth and where is Mabel?
                       - Director/producer John Amiel, heard on NPR