Re: seq in tcp protocol

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2013-03-24 11:29:32 (+0800), ishare <june.tune.sea@xxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs




[Index of Archives]     [Audio]     [Hams]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Fedora Users]

  Powered by Linux