Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!panda!talcott!harvard!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: Help: 4.2bsd IPC routines/TCP sequence error?
Message-ID: <4110@umcp-cs.UUCP>
Date: Sun, 17-Mar-85 09:28:35 EST
Article-I.D.: umcp-cs.4110
Posted: Sun Mar 17 09:28:35 1985
Date-Received: Tue, 19-Mar-85 04:48:23 EST
References: <601@marlin.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 11

Try reading a complete line (rather than anywhere from 1 to 68 bytes,
whichever is available first) in your receiver.  "recv(...)" on a TCP
socket is like read() from a pipe or file: it doesn't *have* to return
a complete "record" since there aren't any records at that level.

In other words, if you want to read exactly 68 bytes from a TCP socket,
loop, read()- or recv()ing, until you've got 68 bytes (or an error).
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland