[Web-SIG] WSGI 2.0
Manlio Perillo
manlio_perillo at libero.it
Thu Oct 4 16:48:18 CEST 2007
Phillip J. Eby ha scritto:
> [...]
>
> WSGI 2.0 does not have a start_response() callable in the first place,
> so none of these apply.
>
I thought that the current WSGI 2.0 draft was only, indeed, a draft.
>
> [...]
>> 4) the environ dictionary should have a new WSGI-defined variable:
>> wsgi.asynchronous.
>> This value should evaluate to true when the server is asynchonous,
>> that is, the WSGI application is executed in the main process loop
>> of the server and the WSGI application can be paused after it yields
>> some data.
>
> It's always the case that a WSGI application can be paused after it
> yields data, even in WSGI 1.0.
I was not aware of this.
It may cause some problems to a unaware WSGI application the fact that a
new "handler" is started "interleaved" with the previous ones.
Regards Manlio Perillo
More information about the Web-SIG
mailing list