[Web-SIG] WSGI 2.0

[James Y Knight]

On Apr 5, 2007, at 10:52 PM, Graham Dumpleton wrote:

> On 06/04/07, James Y Knight <foom at fuhm.net> wrote:
>> What's the point of a switch? If the app didn't provide a content-
>> length, and you can't otherwise determine a content-length (because
>> for example the result is a simple list of strings), just do chunked
>> encoding output automatically.
>
> To a degree that may make sense, but to my mind, the implementation of
> a lower level layer beneath the application, which an application
> writer may have little real control over, should not really be making
> an arbitrary decision on behalf of the user to impose such a
> behaviour. It should always be up to the application writer to make
> the decision.

> That said, it may be worthwhile to actually implement the directive to
> honour Off (default), On or Auto. Thus On is always use chunked
> transfer encoding and Auto would be what you describe. Which approach
> is used though should still be the application writers choice.

But you didn't answer the question: what is the _point_? When do you  
ever want to require a connection close rather than use chunking  
("Off")? Why would you ever want to use chunking if you already know  
the content length ("On"). Those switches seem wholly useless.

No addition or extension to WSGI needed...

James