Interested to Buy Any Domain ? << Click Here >> for more details...
Explain the TIME_WAIT state.
- 1 Answers
- 2636 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 |
What exactly is a socket?
Why do I keep getting EINTR from the socket calls?
What is af_inet in socket?
What exactly does SO_LINGER do?
If bind() fails, what should I do with the socket descriptor?
What is a socket api?
What is a socket set used for?
How to find other end of unix socket connection?
What does af mean in sockets?
How would I put my socket in non-blocking mode?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
Unix Commands 
