Explain the TIME_WAIT state.
- 1 Answers
- 1795 Views
- I also Faced
- E-Mail Answers
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 can I bind() to a port number < 1024?
How would I put my socket in non-blocking mode?
Can multiple clients connect to same socket?
What's better 6pt or 12pt sockets?
How do I properly close a socket?
How do I send [this] over a socket?
What is a deep well socket?
How often should I re-transmit un-acknowleged messages?
Where can a get a library for programming sockets?
How are unix domain sockets implemented?
How do I get the port number for a given service?
How do unix sockets work?
Unix Commands 
