Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!amgraf!cpsolv!rhg
From: rhg@cpsolv.UUCP (Richard H. Gumpertz)
Newsgroups: news.software.b
Subject: Re: Why aren't new articles compressed?
Message-ID: <432@cpsolv.UUCP>
Date: 29 Oct 89 03:18:17 GMT
References: <431@cpsolv.UUCP> <1989Oct27.161920.5169@utzoo.uucp>
Reply-To: rhg@cpsolv.uucp (Richard H. Gumpertz)
Organization: Computer Problem Solving, Leawood, Kansas
Lines: 19

In article <1989Oct27.161920.5169@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>  Our perception was that shortening expiry
>times is generally a more cost-effective way of economizing on disk.

Why not make it an option that each site could choose to enable or disable
depending on the relative cost of disk sectors and CPU cycles at that site?

>There is also a pragmatic issue in that it means modifying *all* the news
>readers.  There are lots of those, many more than you'd think.

Readers would just be modified to look for either nnn or nnn.Z.  Not all that
major.  A given site would switch on compression only after the local readers
had all been fixed.  For small sites, where compression is most likely to
be valuable, there are probably few readers to fix.
-- 
==========================================================================
| Richard H. Gumpertz rhg@cpsolv.uu.NET -or- ...!uunet!amgraf!cpsolv!rhg |
| Computer Problem Solving, 8905 Mohawk Lane, Leawood, Kansas 66206-1749 |
==========================================================================