Explain the TIME_WAIT state.



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

Post New Answer

More Unix Socket Programming Interview Questions

What exactly does SO_REUSEADDR do?

1 Answers  


Whats the difference between select() and poll()?

0 Answers  


How are unix domain sockets implemented?

0 Answers  


What is socket address?

0 Answers  


Why do we need sockets?

0 Answers  






What's better 6pt or 12pt sockets?

0 Answers  


What is a socket address?

0 Answers  


How do I send [this] over a socket?

1 Answers  


How do I properly close a socket?

1 Answers  


system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?

0 Answers  


After the chroot(), calls to socket() are failing. Why?

1 Answers  


How can I read only one character at a time?

1 Answers  


Categories