Path: utzoo!attcan!uunet!husc6!uwvax!dogie!uwmcsd1!ig!agate!ucbvax!VENERA.ISI.EDU!braden
From: braden@VENERA.ISI.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: FTP server question
Message-ID: <8805241545.AA01487@braden.isi.edu>
Date: 24 May 88 15:45:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 18


	
	Unless I misunderstand you there's nothing wrong with the server, it's
	not unusual for a system to produce such a message in two (or more)
	writes and each end up in its own packet, how is the underlying OS
	supposed to know to wait for one more write before shipping the data
	from the first write?
	
Barry,

One might note, just for the record, that both the TCP protocol and most
non-Berkeley implementations of TCP do in fact include a mechanism to
tell the underlying OS when "to wait for one more write before shipping
the data from the first write"... it called PUSH (or PSH). See RFC-793 for
details.  In any case, your basic point that the application level
can have no knowledge of TCP packet boundaries is certainly correct.

Bob Braden