--- On Wed, 11/25/09, Chris Dent <chris.d...@gmail.com> wrote:
> From: Chris Dent <chris.d...@gmail.com>
> I can (barely) relate to some of the complaints that
> start_response is a pain in the ass, but environ, to me, is
> not broken.
I agree. It maps nicely onto the underlying protocol
and WSGI is supposed to be low level right?
The biggest problem with start_response is that after
you evaluate
iterable = application(env, start_response)
Sometimes the start_response has been called and sometimes
it hasn't, and this can break middlewares when they haven't
been tested both ways (repose.who for example seems to
assume it has been called).
By the way, I created a little interface for archiving
notes about wsgi2 here
http://listtree.appspot.com/wsgi2
To add to it you need to fill in a captcha and use the
password "wsgi". I thought I announced this to web-sig
yesterday, but apparently I messed up my reply-to.
If you like, please add something there. I'd be delighted
if you did. I think it might be an interface that is easier
to "scan" than a million emails.
-- Aaron Watters
_______________________________________________
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe:
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
