Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!umd5!dzoey From: dzoey@umd5.umd.edu (Joe Herman) Newsgroups: comp.os.os2.programmer Subject: Re: Problems with IBMs TCP/IP V1.1 for OS/2 Summary: It's not that bad Message-ID: <8364@umd5.umd.edu> Date: 4 Apr 91 20:02:26 GMT References: Organization: University of Maryland, College Park Lines: 24 In article , chlebosc@nadia.stgt.sub.org (Claudius Chlebosch) writes: > I have to write a program, which transfers data using stream sockets in > portions of 32 kByte. The sender should send this portions with one call > to the send() function and the receiver should get this portions with > one call to the recv() function. It sounds like what you want to do is write and read a 32KB *record*. Since you created a *stream* socket, the data you send will arrive as a stream of bytes and it's up to you to put it together as a record. > The server calls the recv() function, which returns with 4360 bytes received. > The client has to call the recv() function once again to get the remaining > 15640 bytes of the segment. In my opinion this behaviour is not correct. It may not be the functionality you want, but it is the correct behavior. Joe Herman U. of Maryland dzoey@terminus.umd.edu -- "Everything is wonderful until you know something about it."