Re: [proposal] add the apr_queue mechanism to apr_socket

2003-01-22 Thread Costin Manolache
Mladen Turk wrote: > > One more... > > Here is the scenario: > > If TC instance is too busy or reached the connection limit the next > connection is refused, causing entire worker to switch to the error > state. This isn't very smart (at least for threaded servers). > I propose that we use the

Re: [proposal] add the apr_queue mechanism to apr_socket

2003-01-22 Thread Jeanfrancois Arcand
Mladen Turk wrote: One more... Here is the scenario: If TC instance is too busy or reached the connection limit the next connection is refused, causing entire worker to switch to the error state. This isn't very smart (at least for threaded servers). I propose that we use the apr_queue to sol

[proposal] add the apr_queue mechanism to apr_socket

2003-01-22 Thread Mladen Turk
One more... Here is the scenario: If TC instance is too busy or reached the connection limit the next connection is refused, causing entire worker to switch to the error state. This isn't very smart (at least for threaded servers). I propose that we use the apr_queue to solve that. The socket wi