Re: ietf-nntp re: batch, streaming, Adding extensions?

Richard Todd <rmtodd@servalan.servalan.com> Tue, 13 August 1996 06:01 UTC

Received: from ietf.org by ietf.org id aa22993; 13 Aug 96 2:01 EDT
Received: from cnri by ietf.org id aa22989; 13 Aug 96 2:01 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa01993; 13 Aug 96 2:01 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id GAA03294 for ietf-nntp-outgoing; Tue, 13 Aug 1996 06:01:38 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id GAA03290 for <ietf-nntp@PHEASANT.ACADEM.COM>; Tue, 13 Aug 1996 06:01:36 -0500
Received: from independence.ecn.uoknor.edu (root@independence.ecn.uoknor.edu [129.15.112.69]) by academ.com (8.7.5/8.7.1) with SMTP id BAA12007; Tue, 13 Aug 1996 01:01:13 -0500 (CDT)
Received: from servalan.UUCP by independence.ecn.uoknor.edu with UUCP (Smail3.1.29.1 #29) id m0uqCUR-00084hC; Tue, 13 Aug 96 00:58 CDT
Received: from [127.0.0.1] by servalan.servalan.com via sendmail with smtp id <m0uqCNX-000f6YC@servalan.servalan.com> for <sob@academ.com>; Tue, 13 Aug 96 00:50:45 -0500 (CDT) (Smail-3.1.91 1996-Mar-5 #1 built 1996-Mar-6)
Message-Id: <m0uqCNX-000f6YC@servalan.servalan.com>
To: Stan Barber <sob@academ.com>
cc: ietf-nntp@academ.com
Subject: Re: ietf-nntp re: batch, streaming, Adding extensions?
In-reply-to: Your message of "Mon, 12 Aug 1996 22:59:24 CDT." <199608130359.WAA10785@academ.com>
Date: Tue, 13 Aug 1996 00:50:41 -0500
Sender: ietf-archive-request@ietf.org
From: Richard Todd <rmtodd@servalan.servalan.com>
X-Orig-Sender: owner-ietf-nntp@academ.com
Precedence: bulk

In message <199608130359.WAA10785@academ.com>you write:
>> > If you can point out two distinct publically available implementations 
>> > that implement this, I'd be delighted.

Do the two distinct implementations have to be of both server and client sides?
Here are some URLs that may be helpful:

    ftp://ftp.math.psu.edu/pub/INN/inn1.4unoff4.tar.gz
       INN 1.4unoff4 release.  The relevant streaming code is in the
	"backends/innxmit.c" and "innd/nc.c" files, I believe.
    ftp://ftp.vix.com/pub/inn/innfeed/innfeed-0.8.5b.tar.gz
       innfeed, a multi-way news feeder program supporting MODE STREAM etc.

>> 
>>         DNEWS, INN, CNEWS
>> With DNEWS it's built in, with INN and CNEWS I understand
>> patches are available, I could be wrong about CNEWS.
>
>That means that the only package you know if that has this functionality
>built-in to the standard release is DNEWS. That seems to contradict your

Depends on whether you call the "unofficial" releases of INN "standard" or
not.  A quick check of one news server's logs shows that 9 out of its 10
peers connected with streaming mode today and are running unoff3 or unoff4;
that's pretty close to "standard" for me.

There was at one time a patch done by Wayne Davison to nntpd 1.5.xxx that 
added, among other things, streaming mode support.  Don't know alas where
you can find it these days; most people who want the substantial performance
boost of streaming mode tend not to run C News/nntpd.

>By "publically available" I mean that either the source code is freely
>available, or there is extensive docuementation freely available on how the
>software works (configuration, protocols, internals). 

Somewhere I think I've got a brief writeup by Jerry Aguirre of what the
relevant commands are (MODE STREAM, CHECK <msgid>, TAKETHIS <msgid>), and
what the possible numeric error codes are.  I'll see if I can dig it up.