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 |
How are unix domain sockets implemented?
Where can a get a library for programming sockets?
What's better 6pt or 12pt sockets?
What is the difference between SO_REUSEADDR and SO_REUSEPORT?
Can a socket have multiple ports?
What does af mean in sockets?
How to find other end of unix socket connection?
What is socket address with example?
Why do not my sockets close?
Whats the difference between select() and poll()?
How come I get address already in use from bind()?
Can multiple sockets use the same port?