[Chicago] Status of wsgi

[Carl Karsten]

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