Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
|
NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
|
|
|
|
TCP Immediate Data Transfer: "Push" Function
(Page 2 of 2)
Forcing Immediate Data Transfer
Naturally, the designers of TCP realized
that a way was needed to handle these situations. When an application
has data that it needs to have sent across the internetwork immediately,
it sends the data to TCP, and then uses the TCP push function.
This tells the sending TCP to immediately push all the data
it has to the recipient's TCP as soon as it is able to do so, without
waiting for more data.
When this function is invoked, TCP
will create a segment (or segments) that contains all the data it has
outstanding, and will transmit it with the PSH control bit set
to 1. The destination device's TCP software, seeing this bit sent, will
know that it should not just take the data in the segment it received
and buffer it, but rather push it through directly to the application.
It's important to realize that the
push function only forces immediate delivery of data.
It does not change the fact that TCP provides no boundaries between
data elements. It may seem that an application could send
one record of data and then push it to the recipient; then
send the second record and push that, and so on. However,
the application cannot assume that because it sets the PSH bit
for each piece of data it gives to TCP, that each piece of data will
be in a single segment. It possible that the first push
may contain data given to TCP earlier that wasn't yet transmitted, and
it's also possible that two records pushed in this manner
may end up in the same segment anyway.
Key Concept: TCP includes a special push function to handle cases where data given to TCP needs to be sent immediately. An application can send data to its TCP software and indicate that it should be pushed. The segment will be sent right away rather than being buffered. The pushed segments PSH control bit will be set to one to tell the receiving TCP that it should immediately pass the data up to the receiving application. |
If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|