Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.toronto.edu!ietf-nntp-distribution-owner
Message-ID: <QcOW0rm6f095QOho8y@turbo.bio.net>
Date: Thu, 27 Jun 1991 13:28:23 -0400
From: lear@turbo.bio.net (Eliot)
Original-To: Jim.Thompson@Central.Sun.COM (Jim Thompson)
Subject: Re: should batch/ibatch/image/et al apply to the article command?
Original-Cc: ietf-nntp@turbo.bio.net
References: <9106251904.AA05493@neuromancer.Central.Sun.COM>
References: <9106251904.AA05493@neuromancer.Central.Sun.COM>
Newsgroups: list.ietf-nntp
Distribution: list
Sender: list-admin@cs.toronto.edu
Approved: list.ietf-nntp@mail.cs.toronto.edu
Lines:       18

Ok.  Here are some comments about your method, Jim.

1.  Setup cost would be higher - establishing an extra TCP connection. 
This is OK, if the NNTP connection is supposed to linger for a long
period of time.

2.  One of the nice things about the existing model is that it could be
implemented on any reliable medium.  Your method pretty much nails it
down to TCP, and protocols that support multiplexing.

3.  Somewhere in there we'll have to exchange byte count information if
the BINARY or IMAGE options are also enabled.  

Now.  What does this buy for 9600 baud connections that normal
IHAVE/SENDME doesn't?

Eliot Lear
[lear@turbo.bio.net]