Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.toronto.edu!ietf-nntp-distribution-owner
From: rsalz@bbn.com (Rich Salz)
Date: Tue, 25 Jun 1991 14:23:54 -0400
Message-ID: <9106251823.AA13463@litchi.bbn.com>
Original-To: ietf-nntp@turbo.bio.net, rickert@cs.niu.edu, sob@tmc.edu
Subject: Re: should batch/ibatch/image/et al apply to the article command?
Newsgroups: list.ietf-nntp
Distribution: list
Sender: list-admin@cs.toronto.edu
Approved: list.ietf-nntp@mail.cs.toronto.edu
Lines:       20

>I would like to see effort spent towards making NNTP a better TRANSPORT.

The following is obnoxious and somewhat self-serving.  I apologize,
but will say it anyway as a way of getting a real data-point in there:

    InterNetNews, currently in beta-test, processes IHAVE at better than
    10 to 20 articles per second for accepting, verifying, storing, and
    arranging for articles to be transmitted.  It can reject more than 100
    duplicates per second.

    INN's implementation techniques aren't for everybody.  Just those
    on the Internet with a reasonable server, like a Sparc-class
    machine.

How much better does NNTP have to be? :-)

More seriously, expending effort to handle unusual cases like
compression or batching might be worthwhile, but the IHAVE transaction
is really quite good.
	/r$