🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.amiga.networking
Article #119

Re: NEW nntp client

#119
From: Michael van Elst
Date: Mon, 23 Oct 1995 20:56
21 lines
1442 bytes
rmal@jet.uk (Richard Lucock) writes:

>It depends on how sophisticated the program structure is, I suppose. I
>can imagine a program that downloads a news header while a separate
>task is examining the previous header to decide whether to take the
>rest of the previous article. Then when the current header is
>finished, the transfer program can download the article from the
>previous header if required. This way the download task is busy all of
>the time, but unwanted article bodies are not transferred.

Yes. But this simple approach is usually slow unless the article
bodies are quite large. The overhead for an additional command
per article can slow transfers significantly and a complex check
for a header field can be slow too (especially the message-id field).

Regards,
-- 
                                Michael van Elst

Internet: mlelstv@serpens.rhein.de
                                "A potential Snark may lurk in every tree."
Technical Details
Message-ID: <46gvhi$ntp@serpens.rhein.de>
Path: arc1-ca.pugleaf.net!comma.rhein.de!serpens!not-for-mail
References: <45tjjm$88g@oban.cc.ic.ac.uk> <rmal.814191054@gen-off-2> <46e2gt$ffs@serpens.rhein.de> <rmal.814462873@gen-off-3>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!comma.rhein.de!serpens!not-for-mail
From: mlelstv@serpens.rhein.de (Michael van Elst)
Newsgroups: comp.sys.amiga.networking,comp.sys.amiga.datacomm,demon.ip.support.amiga
Subject: Re: NEW nntp client
Date: 23 Oct 1995 21:56:18 +0100
Organization: dis-
Message-ID: <46gvhi$ntp@serpens.rhein.de>
References: <45tjjm$88g@oban.cc.ic.ac.uk> <rmal.814191054@gen-off-2> <46e2gt$ffs@serpens.rhein.de> <rmal.814462873@gen-off-3>
NNTP-Posting-Host: serpens.rhein.de