stev@VAX.FTP.COM (05/29/90)
>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 . . . . .
amanda@mermaid.intercon.com (Amanda Walker) (05/29/90)
In article <9005291317.AA01134@vax.ftp.com>, stev@VAX.FTP.COM writes: > we have found that some > applications *really* want certian things in one packet. like vt220 escape > sequences and such . . . Telnet option negotiations are also common > how offensive . . . . . Indeed. Makes me have warm fuzzy feelings about a TCP/IP certification suite... -- Amanda Walker, InterCon Systems Corporation -- "Go not to the elves for counsel, for they will say both no and yes." --J.R.R. Tolkien, The Lord of the Rings