|No such thing as a small change|
Re: How do I do a non-blocking accept?by davidnicol (Acolyte)
|on Aug 23, 2004 at 01:46 UTC||Need Help??|
I was flummoxed by the lack of the nonblocking flags on sockets on microsoft windows, until I realized that inside a nonblocking accept(2) call, accept(2) is just going to have to do something like a select(2).
So a non-blocking accept IS NEVER REQUIRED because you can either
So instead of
you just do do
Or, mock up the accept-em-all-NOW method without clumsily making accept fail:
The difference isby accepting all connections immediately we will possibly have more connections going, more suddenly. If we have a limit on our number of open connections, we only need to check it once per loop to keep from overrunning it.
How much can it affect throughput? It's like asking is it better for an office building to have a one-person revolving door that spins fast or a family-size one that spins slow.