Why does connect() succeed even before my server did an accept()?
- 1 Answers
- 1472 Views
- I also Faced
- E-Mail Answers
Answer / chaitanya
Once you have done a listen() call on your socket, the kernel is primed to accept connections on it. The usual UNIX implementation of this works by immediately completing the SYN handshake for any incoming valid SYN segments (connection attempts), creating the socket for the new connection, and keeping this new socket on an internal queue ready for the accept() call. So the socket is fully open before the accept is done.
The other factor in this is the 'backlog' parameter for listen(); that defines how many of these completed connections can be queued at one time. If the specified number is exceeded, then new incoming connects are simply ignored (which causes them to be retried).
| Is This Answer Correct ? | 0 Yes | 0 No |
How can my client work through a firewall/proxy server?
How do I send [this] over a socket?
Why do I get EPROTO from read()?
What's the difference between a socket and a port?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
What is difference between socket and websocket?
How should I choose a port number for my server?
How do I get the port number for a given service?
How can I read ICMP errors from connected UDP sockets?
Why does connect() succeed even before my server did an accept()?
What is a socket api?
How would I put my socket in non-blocking mode?
Unix Commands 
