Re: seq in tcp protocol
Kristof Provost <[email protected]>
| Newsgroups | org.kernel.vger.linux-newbie |
|---|---|
| Message-ID | <[email protected]> |
On 2013-03-24 11:29:32 (+0800), ishare <[email protected]> wrote: > > TCP is a stream protocol. There is no concept (at the application level > > anyway) of packets in TCP. The receiving TCP/IP stack is free to offer > > the data to the application whenever it decides to, in however many > > lumps as it decides to. Similarly, the sending TCP/IP stack may decide > > to wait to send data until it's received more from the sending > > application before packaging it and sending it to the receiver. > > When one send system api is called , will all data in the buffer > be sent out together at one time ? > No. There are no guarantees about how many TCP packets will be used to send your data, or in how many buffers it will be offered to the application on the receiving side. Kristof -- To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs