[Web-SIG] Re: Latest WSGI Draft (Phillip J. Eby)

[tony at lownds.com]

> (Tony: I'm assuming this was intended for web-sig; discussions like this
> should be archived "for the record".  I hope that's not an issue for you.)
>

Simple oversight, sorry!

>  So, simplifying the job of
> middleware authors, if it doesn't significantly burden framework authors,
> is a good thing here, I think.  (Since the only framework authors who
> would
> be burdened by the change are those who already use  a precisely compliant
> data structure; everyone else had to write a loop anyway.)
>

I agree with that. I liked the simplicity and non-mutability of a sequence
of tuples. Look forward to hearing what a wider audience thinks, after
PEPing!

>>Content-transfer-encoding is assumed to be 7bit if not present, its not
>>required by MIME. 7bit would be wrong for a lot of HTTP responses though.
>
> In the current spec, the server is already required to ensure validity of
> the headers; this would just be a specific mention of one example of that.
>

Ok

-Tony