Xref: utzoo comp.dcom.lans:1397 comp.protocols.tcp-ip:3632
Path: utzoo!utgpu!water!watmath!clyde!ima!spdcc!kaos!romkey
From: romkey@kaos.UUCP (John Romkey)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: Re: FTP server question
Message-ID: <895@kaos.UUCP>
Date: 24 May 88 10:33:05 GMT
References: <535@interlan.UUCP>
Reply-To: romkey@kaos.UUCP (John Romkey)
Distribution: na
Organization: Chaos; Somerville, MA
Lines: 16


Any code which uses TCP which expects TCP to preserve read()/write()
chunking of data (if that's even the abstraction you're using to
communicate with TCP) across the network is BROKEN. TCP doesn't
preserve this information, and anything that expects it to is asking
to lose very loudly.

Even if the application writes a whole block of data in one write(),
there may easily be conditions beyond the control or detection of the
client or server that would cause the TCP to break it up into several
pieces which the other side would see dribbling in as smaller parts
rather than the whole block that was originally written.
-- 
			- john romkey
UUCP: romkey@kaos.uucp			ARPA: romkey@xx.lcs.mit.edu
 ...harvard!spdcc!kaos!romkey		Telephone: (617) 776-3121