Interested to Buy Any Domain ? << Click Here >> for more details...
Explain the TIME_WAIT state.
- 1 Answers
- 2582 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 many socket connections can a server handle?
What is af_inet in socket?
When should I use UDP instead of TCP?
What's better 6pt or 12pt sockets?
What are Sockets?
What exactly is a socket?
What is a socket connection?
Where can a get a library for programming sockets?
How come I get address already in use from bind()?
of the socket? Does doing a connect() call affect the receive behaviour?
What exactly does SO_LINGER do?
How can I set the timeout for the connect() system call?
Unix Commands 
