Interested to Buy Any Domain ? << Click Here >> for more details...
Why does connect() succeed even before my server did an accept()?
- 1 Answers
- 2027 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 is socket address?
What is a socket file?
Is a socket a file?
What is a deep well socket?
Why does it take so long to detect that the peer died?
How to find other end of unix socket connection?
Can a socket have multiple ports?
Where is the socket located?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
What is a socket api?
What is the difference between read() and recv()?
How many sockets can a cpu have?
What does af mean in sockets?
What is a socket set used for?
How is a socket created?
