Glyph,
Belated (I was in the thick of a few unrelated crises) thanks - it helps to
understand a little bit of the background on the way it works. I have made
adjustments and everything works the way I was hoping for now.
I wish I understood it a little better, if for no other reason than to
cont
I tried to find out if there is a way to limit the thread pool size from
command line for twisted web and found nothing. Does it exist?
On Mon, Nov 19, 2018 at 8:30 AM Jean-Paul Calderone <
exar...@twistedmatrix.com> wrote:
> On Mon, Nov 19, 2018 at 8:26 AM Maarten ter Huurne
> wrote:
>
>> On ma
On Mon, Nov 19, 2018 at 8:26 AM Maarten ter Huurne
wrote:
> On maandag 19 november 2018 12:40:20 CET Darren Govoni wrote:
> > Hi,
> > I am using twisted to run my Flask app via WSGI like so.
> >
> > twistd --pidfile $PORT/pidfile -l $PORT/logfile -n web --port
> > tcp:$PORT --wsgi my.app
> >
>
On maandag 19 november 2018 12:40:20 CET Darren Govoni wrote:
> Hi,
> I am using twisted to run my Flask app via WSGI like so.
>
> twistd --pidfile $PORT/pidfile -l $PORT/logfile -n web --port
> tcp:$PORT --wsgi my.app
>
> Naturally, I have functions representing routes that enter and exit
> j
Hi,
I am using twisted to run my Flask app via WSGI like so.
twistd --pidfile $PORT/pidfile -l $PORT/logfile -n web --port tcp:$PORT
--wsgi my.app
Naturally, I have functions representing routes that enter and exit just
fine.
However, I notice the twisted daemon process is :"gathering threads
