Re: seq in tcp protocol

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

 



On Sat, Mar 23, 2013 at 02:31:18PM +0100, Kristof Provost wrote:
> On 2013-03-22 21:30:08 (+0800), ishare <june.tune.sea@xxxxxxxxx> wrote:
> >   If I send a  buffer with tcp protocol , the data is separated to serveral packets ,
> >   each packet will have a seq number with it ,which ensures the recipient read this buffer
> >   in right orfer .
> > 
> >   my question is : how the recipient know which is the end packet of this queue ? Is there 
> >   data indicate the total quantity of packets composing this buffer ?
> > 
> 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 ?

  
> 
> You may find http://en.wikipedia.org/wiki/Nagle%27s_algorithm
> interesting.
> 
> Regards,
> 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