Explain the TIME_WAIT state.
Answer / chaitanya
Remember that TCP guarantees all data transmitted will be delivered, if at all possible. When you close a socket, the server goes into a TIME_WAIT state, just to be really really sure that all the data has gone through. When a socket is closed, both sides agree by sending messages to each other that they will send no more data. This, it seemed to me was good enough, and after the handshaking is done, the socket should be closed. The problem is two-fold. First, there is no way to be sure that the last ack was communicated successfully. Second, there may be "wandering duplicates" left on the net that must be dealt with if they are delivered.
| Is This Answer Correct ? | 1 Yes | 0 No |
What is the difference between SO_REUSEADDR and SO_REUSEPORT?
What's the difference between impact sockets and regular sockets?
What is the difference between connected and unconnected sockets?
How do I properly close a socket?
Can multiple clients connect to same socket?
How can I read ICMP errors from connected UDP sockets?
Why do we need socket programming?
How is a socket created?
How do I get the port number for a given service?
Can a socket have multiple ports?
How many socket connections can a server handle?
What is socket programming in java?