Xref: utzoo comp.dcom.lans:1406 comp.protocols.tcp-ip:3642
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!tness7!bellcore!faline!thumper!karn
From: karn@thumper.bellcore.com (Phil R. Karn)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: Re: FTP server question
Summary: but the server's TCP isn't exactly kosher either
Message-ID: <1106@thumper.bellcore.com>
Date: 25 May 88 05:31:38 GMT
References: <535@interlan.UUCP> <22806@bu-cs.BU.EDU>
Distribution: na
Organization: Bell Communications Research, Inc
Lines: 8

While it is certainly true that a client that expects any sort of
relationship between TCP segments and logical messages is broken, I
wouldn't let the server get off the hook that easily. Why should it take
two packets to send what should go in one? In this, the first year AJ
(After Jacobson) I would think people would be a little more aware of
such inefficient TCP behavior. :-)

Phil