Has anyone written any thread-management middleware components for WSGI?
Many web applications need to run application code in separate threads.
Often, the number of threads needs to be limited, either by throttling
the rate of thread creation, or by dispatching requests to a thread pool.
This is
Jim Fulton wrote:
> Has anyone written any thread-management middleware components for WSGI?
> Many web applications need to run application code in separate threads.
> Often, the number of threads needs to be limited, either by throttling
> the rate of thread creation, or by dispatching requests t
Ian Bicking wrote:
> Jim Fulton wrote:
>
>> Has anyone written any thread-management middleware components for WSGI?
>> Many web applications need to run application code in separate threads.
>> Often, the number of threads needs to be limited, either by throttling
>> the rate of thread creation,
Jim Fulton wrote:
>> Right now all threading and generally concurrency is handled by the
>> server. Since it *has* to be handled by the server,
>
>
> Why does it have to be handled by the server?
Because most WSGI apps are blocking, so unless you want the server to be
non-concurrent it has to
Ian Bicking wrote:
> Jim Fulton wrote:
>
>>> Right now all threading and generally concurrency is handled by the
>>> server. Since it *has* to be handled by the server,
>>
>>
>>
>> Why does it have to be handled by the server?
>
>
> Because most WSGI apps are blocking, so unless you want the s
