[Web-SIG] WSGI 2.0

[Manlio Perillo]

Manlio Perillo ha scritto:
> Ian Bicking ha scritto:
>> [...]
>>> Ok, here is more useful definition.
>>>
>>> If wsgi.asynchronous evaluates to true, then the WSGI application 
>>> *will* be executed into the server main process cycle and thus the 
>>> application execution *will* be interleaved (since this is the only 
>>> way to support multiple concurrent requests).
>> Isn't the more important distinction that the application must not 
>> block?  Kind of like wsgi.multithread means the application must be 
>> threadsafe.
>>
> 
> Right, but I assume that this is evident when I say "executed into the 
> server main process cycle".
> 
> An interesting example is an application that will read some data from a 
> source (as an example from a video capture device) and will send the 
> output to the web.
> 

Forget what I have written.

A request specific context is already supplied by the wsgi application 
callable context.

I'm tring to understand if an explicit request context is necessary for 
some other kind of applications.



Regards  Manlio Perillo