OK, it makes sense that if the client isn reading, the data isn going to make it across the connection. I take it this causes the sender to block after the recieve queue is filled?
The sender blocks when the socket send buffer is full, so buffers will be full at both ends. While the window is closed, the sending TCP sends window probe packets. This ensures that when the window finally does open again, the sending TCP detects the fact. [RFC1122, ss 4.2.2.17] The second interesting case is “Nagle algorithm” (small segments, e.g.
Related Questions
- OK, it makes sense that if the client isn reading, the data isn going to make it across the connection. I take it this causes the sender to block after the recieve queue is filled?
- Is it ok to overfill the database (going over the allocation) to increase chances of getting data in different sky conditions?
- What if the connection is congested with backup data?
