[Web-SIG] WSGI 2.0

James Y Knight foom at fuhm.net
Fri Mar 30 19:26:02 CEST 2007

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 out early.
> I'd like to have fewer optional things, rather than more, so I  
> think we should either require a dedicated thread or make it non- 
> dedicated.  It should be quite straightforward to implement a  
> middleware component that ensures its wrappee is run entirely  
> within a dedicated thread, using a Queue.

You can't *require* the server to switch threads every iteration. In  
fact I'm willing to bet many servers will continue using a dedicated  
thread even if they're explicitly allowed to not do so. So having  
some indication as to which the server is doing might be helpful.


More information about the Web-SIG mailing list