Why does connect() succeed even before my server did an accept()?
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 I write a multi-homed server?
What is the difference between a socket and a port?
Explain the TIME_WAIT state.
How do I send [this] over a socket?
What exactly does SO_REUSEADDR do?
How can I listen on more than one port at a time?
Why do I get connection refused when the server is not running?
What is a socket file?
How are unix domain sockets implemented?
Why do we need sockets?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
How does a socket work?