[Web-SIG] When must applications call the WSGI start_response callable.

I'm a bit unclear about the timing of the start_response call. I think this is because the PEP is unclear, but perhaps I missed something. It doesn't appear that the PEP says when the start_response callable must be called. It gives several examples. In most, the callback is called when the

Re: [Web-SIG] When must applications call the WSGI start_response callable.

Jim Fulton wrote: I'm a bit unclear about the timing of the start_response call. I think this is because the PEP is unclear, but perhaps I missed something. It doesn't appear that the PEP says when the start_response callable must be called. It gives several examples. In most, the callback

Re: [Web-SIG] When must applications call the WSGI start_response callable.

On Dec 15, 2005, at 3:01 PM, Jim Fulton wrote: Normally an application will call the start_response callable when the application is called or when the result iterator is constructed, as shown in the first 2 examples. An application, or more commonly, a middleware component that provides it's

Re: [Web-SIG] When must applications call the WSGI start_response callable.

Ian Bicking wrote: Jim Fulton wrote: ... Why do I want this? It appears that this would be needed to enable middleware components that manage application threads. I can imagine though that there aren't any existing servers that handle what I've suggested correctly. I do think it would be