Re: ietf-nntp Initial draft FINALLY available
Ramanan <ramanan@sprint.net> Wed, 02 October 1996 15:01 UTC
Received: from cnri by ietf.org id aa07195; 2 Oct 96 11:01 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa11535;
2 Oct 96 11:01 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
JAA24312 for ietf-nntp-outgoing; Wed, 2 Oct 1996 09:53:56 -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 JAA24308 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 2 Oct 1996 09:53:54 -0500
Received: from fire1.sprintlink.net (fire1.sprintlink.net [206.229.244.2]) by
academ.com (8.7.6/8.7.1) with SMTP id JAA24364;
Wed, 2 Oct 1996 09:53:51 -0500 (CDT)
Received: from fire2.int.sprintlink.net ([206.229.244.28]) by
fire1.sprintlink.net
via smtpd (for ACADEM.COM [198.137.249.2]) with SMTP; 2 Oct 1996 14:55:30 UT
Received: from ra.int.sprintlink.net ([206.229.253.110]) by
fire2.int.sprintlink.net
via smtpd (for ACADEM.COM [198.137.249.2]) with SMTP; 2 Oct 1996 14:57:22 UT
Received: (from ramanan@localhost) by ra.int.sprintlink.net (8.6.9/8.6.9) id
KAA04082; Wed, 2 Oct 1996 10:52:44 -0400
Date: Wed, 2 Oct 1996 10:52:44 -0400 (EDT)
From: Ramanan <ramanan@sprint.net>
X-Sender: ramanan@ra.int.sprintlink.net
To: Stan Barber <sob@academ.com>
cc: Ben Polk <bpolk@netscape.com>, ietf-nntp@academ.com
Subject: Re: ietf-nntp Initial draft FINALLY available
In-Reply-To: <199610020437.XAA15568@academ.com>
Message-ID: <Pine.SUN.3.90.961002103843.4001B-100000@ra.int.sprintlink.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
Stan: > > > 12.4 NEWNEWS > > > > Do we have to keep this? It really doesn't work in a practical way in some > > of the widely used NNTP implementations. > > > Any other opinions about this. NEWNEWS is used by sites using pull/slurp. Most ISPs who use INN have some concerns allowing the NEWNEWS command. INN itself being a heavy resource utilizing process, the way NEWNEWS is implemented causes several thousand directory lookups and history file lookups. This adds to the burden on the machine. Most people disable NEWNEWS if they dont support pull/feed capabilities. Causing this command to be not there in RFC would force you to come up with something else that will support pull feeders ? Or may be it is time for pull-feed software developers to use a better slurping mechanism and they can help contribute to the RFC. Or even better, that you could have it for now and we can have more discussion on this before removing or keeping this command. But I know that some big News providers do support NEWNEWS. I dont support it yet, but have been thinking of supporting it due to an increasing number of requests for pull feeds. Regards, --Ramanan
- ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available Chris Caputo
- Re: ietf-nntp Initial draft FINALLY available James Fidell
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ramanan
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Nat Ballou
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Bob Sloane
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Thomas 'Mike' Michlmayr
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Bob Sloane
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available William H. Magill
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available USENET news manager
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available chris (c.) lewis
- Re: ietf-nntp Initial draft FINALLY available William H. Magill
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- ietf-nntp XHDR versus XPAT USENET news manager