Date: Fri, 15 Nov 1996 10:17:03 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: fenner@parc.xerox.com (Bill Fenner) Cc: scrappy@ki.net, jdp@polstra.com, hackers@FreeBSD.org Subject: Re: Sockets question... Message-ID: <199611151717.KAA26280@phaeton.artisoft.com> In-Reply-To: <96Nov14.180824pst.177557@crevenia.parc.xerox.com> from "Bill Fenner" at Nov 14, 96 06:08:23 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> TCP is not a record-oriented protocol, and will buffer up (or re-packetize > however it wants) any data that you give it. Therefore, you have to be > prepared to read whatever size it wants to give you, and your application > has to be able to put it back together into what it wants. Your data will > all get there, eventually. Then why do we have all of the silly frag reconstruction code in the packet receive path, if having the code makes no difference? > my part anyway. What you need to do is write all your data to the network, > and not count on it arriving in the same sized chunks as you wrote it. > But it will all arrive. ?!? This is (supposedly) what happens *for you* during packet reassembly on the receiving end. Packets, as they arrive, are reassembled, in order, into the user buffer, so the user buffer on the receiver ends up looking thesame as the user buffer on the sender. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611151717.KAA26280>