Interested to Buy Any Domain ? << Click Here >> for more details...
Explain the TIME_WAIT state.
- 1 Answers
- 2501 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 force a socket to send the data in its buffer?
Explain the TIME_WAIT state.
Why does connect() succeed even before my server did an accept()?
How can I read ICMP errors from connected UDP sockets?
Can a single socket port be used for multiple applications?
How are unix domain sockets implemented?
How do unix sockets work?
What is active unix domain sockets?
Why sockets are used?
What is a socket address?
Why do we need socket programming?
What is the difference between connected and unconnected sockets?
Unix Commands 
