At 11:08 PM 3/29/2007 -0400, James Y Knight wrote:
>On Mar 29, 2007, at 10:41 PM, Phillip J. Eby wrote:
>>>It's not clear if the app_iter must be used in the same thread as the
>>>application. Since the application is blocking, presumably *it*
>>>must be
>>>run all in one thread. This should be m
At 11:30 PM 3/29/2007 -0500, Ian Bicking wrote:
>Phillip J. Eby wrote:
>>At 07:56 PM 3/29/2007 -0500, Ian Bicking wrote:
>>>Do we want to discuss WSGI 2.0? I added a wiki page here to list
>>>anything anyone wants to discuss for 2.0: http://wsgi.org/wsgi/WSGI_2.0
>>>
>>>I've listed the things I ca
On Mar 30, 2007, at 12:46 PM, Phillip J. Eby wrote:
>> I suppose another flag could be added "wsgi.dedicated_thread"
>> which is True only if every call to .next will be on the same thread
>> as the call to your app. Of course that doesn't really help an app
>> broken by it, just lets them error o
RFC 2145 says:
"An implementation of HTTP/x.b sending a message to a
recipient whose version is known to be HTTP/x.a, a < b,
MUST NOT depend on the recipient understanding a header
not defined in the specification for HTTP/x.a. For example,
HTTP/1.0 clients cannot be expected to und
Phillip J. Eby wrote:
> I was thinking of something a bit simpler; the environ key would be an
> object that, when called, tells the server that it's okay to resume
> iteration attempts on the application. A sort of "put me back on the
> queue for iteration" call. The callback would have to be
At 12:42 PM 3/30/2007 -0500, Ian Bicking wrote:
>Phillip J. Eby wrote:
>>I was thinking of something a bit simpler; the environ key would be an
>>object that, when called, tells the server that it's okay to resume
>>iteration attempts on the application. A sort of "put me back on the
>>queue fo
