Quartz is certainly powerful, but I think it's outside the scope of something
we want in a WSGI spec. Is there a specific feature you're referring to?
- Original Message -
From: Nam Nguyen bits...@gmail.com
To: Timothy Farrell tfarr...@owassobible.org
Cc: P.J. Eby p...@telecommunity.com
- Original Message -
From: P.J. Eby p...@telecommunity.com
To: Timothy Farrell tfarr...@owassobible.org, web-sig@python.org
Sent: Friday, January 7, 2011 2:14:20 PM
Subject: Re: [Web-SIG] PEP 444 feature request - Futures executor
There are some other issues that might need
When I originally requested a futures executor option (the email that started
this thread), this is more like what I had in mind. I'm not against
async...rather indifferent. But I wanted the ability for the server to run
something after the response had been fully served to the client and
There has been much discussion about how to handle async in PEP 444 and that
discussion centers around the use of futures. However, I'm requesting that
servers _optionally_ provide environ['wsgi.executor'] as a futures executor
that applications can use for the purpose of doing something after
if an application called
executor.shutdown(). This doesn't seem difficult to my tiny brain.
- Original Message -
From: Guido van Rossum gu...@python.org
To: Timothy Farrell tfarr...@owassobible.org
Cc: web-sig@python.org
Sent: Friday, January 7, 2011 11:59:10 AM
Subject: Re: [Web-SIG] PEP 444
- Original Message -
From: P.J. Eby p...@telecommunity.com
To: Timothy Farrell tfarr...@owassobible.org, web-sig@python.org
Sent: Friday, January 7, 2011 2:14:20 PM
Subject: Re: [Web-SIG] PEP 444 feature request - Futures executor
This seems like a potentially good way to do it; I
Hello web-sig. My name is Timothy Farrell. I'm the developer of the Rocket
web server. I understand that most of you are more experienced and passionate
than myself. But I'm come here because I want to see certain things
standardized. I'm pretty new to this forum but I've read through all
