Why does connect() succeed even before my server did an accept()?
Answer Posted / 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 |
Post New Answer View All Answers
How is a socket created?
What's the difference between a socket and a port?
What is socket address with example?
Why do we need sockets?
What is active unix domain sockets?
What pieces of information make up a socket?
What is the purpose of socket?
How can I tell when a socket is closed on the other end?
Why does the sockets buffer fill up sooner than expected?
Why sockets are used?
How many sockets can a cpu have?
Can multiple sockets use the same port?
How do I use TCP_NODELAY?
What exactly is a socket?
What are the pros/cons of select(), non-blocking I/O and SIGIO?