pan-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Pan-users] "Fit to window" - image view enhancement


From: Jim Reiss
Subject: Re: [Pan-users] "Fit to window" - image view enhancement
Date: Wed, 2 Apr 2003 09:38:57 -0700 (MST)

> On Wed 02 Apr 2003 01:22, Grzegorz B. Prokopski posted as excerpted below:
> > PS: In my old netscape I had "remove expired articles" option
> > that was removing all non-existant-on-server articles from the list.
> > I can't find it's equivalent in Pan - am I blind? =)
> > Oh - I don't think that "remove articles +5 days old" is an equivalent.
> 
> [Replied to both list and above author, as requested.]
> 
> PAN doesn't have this option, because it does it automatically, it would 
> seem.  
> Least-wise, it removes articles no longer on the server here, when I fetch 
> new overviews.
> 
> Actually, that's a bit frustrating to some, particularly those who like 
> archives of text groups going back a year or more, when the server doesn't 
> have that sort of retention.
On the flip side, Pan is still pretty slow in handling large sets of
headers, so keeping such an archive would be just asking for performance
and memory problems.

I suspect, by the way, that the "memory leak" problem that's been
discussed lately may just be a simple "not enough memory" problem.  Pan
loads all the headers into memory for sorting and other processing, and
when you're simultaneously downloading headers from several large groups
it is going to use a heck of a lot of memory.  If that's the case, and
even if it isn't, I think it would be a very good idea to have the
option to limit header downloading to a single connection.  Any unused
connections would be allocated to article downloads only.  Besides the
memory usage issue, this would be great for news servers that are slow
for header downloads (if all connections are for header downloads you
may only use a fraction of your bandwidth until the headers are all
retrieved, but if you mix in articles then you maximize throughput).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]