Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!ucsd!ucbvax!VAX.FTP.COM!stev
From: stev@VAX.FTP.COM
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Mail problem KA9Q->Interactive/386 Unix
Message-ID: <9005291317.AA01134@vax.ftp.com>
Date: 29 May 90 13:17:14 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 13

>The fault is definitely on the Interactive UNIX end. TCP is a pure byte
>stream protocol, and it is allowed to packetize data for transmission in any
>way it chooses.  Applications are required to read incoming data from a TCP
>connection without regard to packet boundaries. For example, a SMTP receiver
>that reads a line of text must do so by reading a character at a time from
>the receive buffer until it sees a cr/lf sequence. Anything else in the
>receive queue must be left undisturbed until the next read operation.

while in a perfect world this would be true, we have found that some
applications *really* want certian things in one packet. like vt220 escape
sequences and such . . .

how offensive . . . . .