c++ - Winsock 200ms delay issue -
I know that WinSock send call
may be delayed from MSDN:
Naval Algorithm: S_Algorithm
Problem Summary : If the short message with the SOSNDBUF "0" option again (& lt; MTU), Function Block 200ms. My question : Why send a message first Delay 200ms? Because TCP is inactive before sending it first, I think the first message should be sent immediately. But the results of the test are not desired. Why delay 200ms in the first message, Thanks for the answer. Add some details : Nagllog algorithm works for small messages such as the following: So, I hope that the first message sends immediately and the second message waits for the first message of 200 ms for the acc. Is this wrong? Typically TCP puts data in buffer as long as the action is not performed by peer. In your case the sender is not buffer (due to SO_SNDBUF = 0), so TCP blocks the sender to keep data for potential dispatch. Coworkers' TCP stacks use "delayed AK" routine, and accept 200 msec delay (or 2 packets without data after receiving without acking). The sender will be blocked until all data is accepted by peer. The network's RTT is long, or if the packet is lost, it can take more than 200 meters.
1 If the wire is useless , Then send it immediately. 2. If ACK has not been received for formal message, then ACK & amp; Send 3. TCP Aluminum William McKenzie send the ACC after 200 mms of the window.
Comments
Post a Comment