> On Jul 17, 2018, at 22:40, Jonathan Vanasco wrote:
>
>
>
> On Tuesday, July 17, 2018 at 7:46:59 PM UTC-4, Bert JW Regeer wrote:
> The threads that run the WSGI app are pre-spawned, they wait on a new request
> to be added to a queue, peel one off, pass it down the WSGI app, and then
>
On Tuesday, July 17, 2018 at 7:46:59 PM UTC-4, Bert JW Regeer wrote:
>
> The threads that run the WSGI app are pre-spawned, they wait on a new
> request to be added to a queue, peel one off, pass it down the WSGI app,
> and then back.
> ...
> What are you trying to do with a "max requests"?
>
The threads that run the WSGI app are pre-spawned, they wait on a new request
to be added to a queue, peel one off, pass it down the WSGI app, and then back.
There are no other "workers". The rest is a simple asyncore loop, whereby
requests are accepted, and added to the list of sockets to
does anyone know if the workers in waitress are spawned as-needed for each
request, or if they are pre-spawned and answer requests when available?
I think it is the latter. if so, is there a reasonable chance of having a
max-requests feature implemented (or would this be possible to kludge
