On Wed, 2010-02-03 at 14:35 +0530, Asankha C. Perera wrote: > Hi Ortwin > > What you are referring to is the "backlog" of a Socket. That is the number > > of > > half-open / unaccepted connections that is queued by the OS before sending > > RSTs > > for any more SYNs. > > > I thought so too.. but I think in the NIO model its a bit different - > especially when a request is handled by a separate thread pool. In the > classic model of a thread per socket - an implementation will not be > doing a ServerSocket.accept() once the thread pool is exhausted. > However, the NIO reactor will process events over threads that are > different from the worker threads processing the request. Thus I believe > all connections gets accepted by default - without being queued at TCP > level, and this is what I would like to control if possible.. provided > that my understanding on this is correct :D >
Asankha I think NIO should work quite similarly. A selectable channel can be marked as OP_ACCEPT ready, but that does not mean the connection listener must accept that connection or accept it immediately. Hope this helps Oleg > thanks > asankha > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
