Why does connect() succeed even before my server did an accept()?
- 1 Answers
- 1727 Views
- I also Faced
- E-Mail Answers
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
What does af mean in sockets?
How do unix sockets work?
How can I set the timeout for the connect() system call?
How many socket connections can a server handle?
What is a socket file?
What is the purpose of socket?
What is a socket set used for?
How many sockets can a port have?
Why does it take so long to detect that the peer died?
Why do I get EPROTO from read()?
What is a deep well socket?
What's better 6pt or 12pt sockets?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
How many sockets can a cpu have?
How does unix socket work?
