After reading this post about the inherent problems of TCP connection termination, I almost feel sorry for the protocol. It seems to be trying so hard, but doomed for inevitable failure.
Martin Sustrik goes through all the reasons this is problematic in great detail. His main takeaway is that the symmetrical nature of TCP termination call can’t be consistently reliable. Really well thought out, plus the diagrams really help visualize a lot of the problems.
Martin Sustrik comments:
The shortcomings of TCP connection termination have been described many times. If you are not familiar with those problems here’s an example of an article that focuses on the problem.
However, there’s one special use case that is rarely, if ever, discussed.
Imagine a TCP client wanting to shut down its TCP connection to server cleanly. It wants to send the last request to the server, read any responses it may produce and exit.
Given that it has no idea how many responses are about to arrive it can’t just close the socket (it would miss the responses) but, at the same time, it cannot just go on reading responses forever (that would make it hang after the last response is received). What it needs is some way to let server know that it is shutting down. The server should then send back all the pending responses and subsequently acknowledge the shut down.
Read more at: Why is my TCP not reliable (expert edition)
- Dan Frith – IT Origins - April 26, 2018
- Low Fat Windows | Gestalt IT Rundown: April 25, 2018 - April 25, 2018
- The Fault, Dear Troy, is not in our IRL Analogies, But In Ourselves - April 24, 2018
- All Your Networking Are Belong to NFV | The On-Premise IT Roundtable - April 24, 2018
- Hass.io Changing OS - April 23, 2018
- Flickr, SmugMug, and SaaS - April 23, 2018
- E8 Storage Announces InfiniBand Support - April 20, 2018
- Cisco’s Latest AP Comes With A History Lesson - April 20, 2018
- Droplet Computing: Living La Vida Legacy - April 20, 2018
- Trends – IT Origins Survey - April 19, 2018