[news.software.readers] Re: Mozilla blamed for overload on newsservers

[Per Abrahamsen <abraham@dina.kvl.dk>]

Could we do something like this in Gnus?  

There is a high-traffic group with 60 days expire I read daily, and
fetching the headers takes time, even though the server is on the
local network. 

[ Just because Mozilla does it, doesn't mean it's bad. ]

------- Start of forwarded message -------
From: Phil Peterson <phil@netscape.com>
Newsgroups: news.software.readers
Subject: Re: Mozilla blamed for overload on newsservers
Date: Sat, 05 Apr 1997 18:19:05 -0800
Organization: Netscape Communications Corp.
Message-ID: <33470819.91FC6F59@netscape.com>
References: <3342D596.AF8@xs4all.nl> <3343F6D9.BD0EC0F1@netscape.com> <5i15oj$bah@nnrp1.news.primenet.com> <334478C6.7E33675@netscape.com> <5i3lnt$l3p@nnrp1.news.primenet.com>

billy@mix.com wrote:
> 
..snip..
> Well.. you folks seem to do pretty caching web pages, why aren't you
> caching this stuff too?  XOVER reads are a heck of a lot faster when
> one only requests what's new to them.  My feeling is this places the
> burden where it belongs, on the user's machine, not the server.  Yes
> this won't catch articles canceled in between reads and probably has
> some other problems - perhaps you could read in the new records first
> then go back and refresh the old data..?

Way ahead of you. Communicator/4.0 does cache header information on the
local disk. We only XOVER new stuff when you open the group. 

In the 2.x/3.x newsreader, there was no local header cache, so Show All
Messages had to go XOVER every article in the group. This is not the
case in 4.0.

-- Phil.
------- End of forwarded message -------