Interested to Buy Any Domain ? << Click Here >> for more details...
Explain the TIME_WAIT state.
- 1 Answers
- 2572 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 do Sockets Work?
How can I write a multi-homed server?
If bind() fails, what should I do with the socket descriptor?
Why sockets are used?
What is the purpose of socket?
Why does it take so long to detect that the peer died?
How do I properly close a socket?
What exactly does SO_LINGER do?
Why do I get connection refused when the server is not running?
over the socket? Is there a way to have a dynamic buffer? What does one do when one does not know how much information is coming?
What pieces of information make up a socket?
How can I force a socket to send the data in its buffer?
Unix Commands 
