🚀 go-pugleaf

In article <816077534snz@keris.demon.co.uk>
           chris@keris.demon.co.uk "Chris Croughton" writes:
> 
> If you (or anyone else) can come up with a good algorithm to decide when
> "everything's finished", I'd like to hear it - my machine runs
> unattended most of the time, and those extra 2 minutes at the end of the
> session add up...
> 
I have noticed from running NNTP that it fetches the headers for news 
first. There are two figure quoted in the messages that relate to downloading 
news and the headers give the total number of articles to be expected. If mail 
is going to be transferred in parallel and the news is still going after mail 
has been dealt with then this would be one way. When (xxx/yyy) is presented 
with the two numbers xxx and yyy equal in value then it is time to apply just a 
short pause before logging off. It will mean that mail not completed transfer 
will have to wait till next time.

Of course a chat to demon might get them to put an indication of mail items to 
be received with each mail item carrying this field. If new mail is arriving 
during the download it could update the total when it adds the newly arriving 
message to the queue. This would then be a zero terminated process. A similar 
thing could be done for up-loads.

-- 
Paul E. Bennett
(peb@transcontech.co.uk)
Going Forth Safely