subject:"Re\: \[Web\-SIG\] wsgi write=start_response\(\) and iterable return\?"

Re: [Web-SIG] wsgi write=start_response() and iterable return?

2010-01-04 Thread Aaron Watters

> From: Aaron Watters > > If an application returns an iterable response and *also* > calls the write()... what is supposed to happen? After carefully considering all the responses on this issue ;c) I came up with the following strategy for dealing with calls to write() in combination with

Re: [Web-SIG] wsgi write=start_response() and iterable return?

2010-01-04 Thread P.J. Eby

At 08:42 AM 1/4/2010 -0800, Aaron Watters wrote: > From: Aaron Watters > > If an application returns an iterable response and *also* > calls the write()... what is supposed to happen? After carefully considering all the responses on this issue ;c) I came up with the following strategy for

Re: [Web-SIG] wsgi write=start_response() and iterable return?

2010-01-05 Thread Aaron Watters

--- On Mon, 1/4/10, P.J. Eby wrote: > From: P.J. Eby > Subject: Re: [Web-SIG] wsgi write=start_response() and iterable return? > To: "Aaron Watters" , web-sig@python.org > Date: Monday, January 4, 2010, 4:38 PM > At 08:42 AM 1/4/2010 -0800, Aaron > Watters wrote: