[Chicago] Status of wsgi
japhy at pearachute.com
Thu Oct 11 20:30:30 CEST 2012
When you're doing something like comet polling, "sitting around doing
nothing" means blocking the client request until you have data to return,
versus closing the connection and having the client repeatedly send
You're correct, it's mostly a resource optimization, but it can be
significant if you're trying to handle lots of clients in real time.
It was mentioned earlier in the thread, but tornado is a great example of
WSGI and async living together in a single python webapp.
On Thu, Oct 11, 2012 at 1:25 PM, Carl Karsten <carl at personnelware.com>wrote:
> On Wed, Oct 10, 2012 at 11:14 PM, Jordan Bettis <jordanb at hafd.org> wrote:
> > But if there's no mechanism for setting the request aside, the the
> > worker thread has to sit around doing nothing while the search server
> > does its thing. An asynchronous framework would let the worker set the
> > request aside and process new requests while it's waiting for the
> > response from the search server.
> What is the difference between "sit around doing nothing" and "setting
> the request aside" ?
> I am guessing there is a resource (memory, connections, stack?) issue,
> but I don't really see how either model is going to be much different,
> so I must be missing something.
> Carl K
> Chicago mailing list
> Chicago at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Chicago