Explain the TIME_WAIT state.
- 1 Answers
- 2065 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 I get my server to find out the clients address / host- name?
What is the difference between connected and unconnected sockets?
When should I use shutdown()?
What is the purpose of socket?
Where is the socket located?
How many socket connections can a server handle?
What is a sae socket?
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 are Sockets?
How is a socket created?
After the chroot(), calls to socket() are failing. Why?
Why does the sockets buffer fill up sooner than expected?
Unix Commands 
