Fwd: HTTP/2 and WSGI

[Russell Keith-Magee]

Hi all,

I have been contacted by Robert Collins, who is trying to get a working group together to discuss HTTP/2 and WSGI. 

Attached is the forwarded email from Robert with the kickoff details.

Historically, Django hasn't been deeply involved in process of developing WSGI and related standards; this is an opportunity for us to change that trend.

Yours,

Russ Magee %-)

---------- Forwarded message ----------
From: Robert Collins <rob...@robertcollins.net>
Date: Sat, Sep 20, 2014 at 6:00 AM
Subject: HTTP/2 and WSGI
To: Graham.D...@gmail.com, rus...@keith-magee.com, chr...@plope.com, armin.r...@active-4.com, bche...@gmail.com, rob...@unbit.it
Cc: Nick Coghlan <ncog...@gmail.com>


Hi gentle-folk, I'd like to draw your attention to
https://mail.python.org/pipermail/web-sig/2014-September/005244.html
wherein I am trying to get a working group of folk together to prep
WSGI for HTTP/2's new capabilities.

Nick pointed out that it would be a terrible thing to do this work and
then have major servers and frameworks hate on it because its not
going to work for them.

If you've limited time but can commit to e.g. reviewing drafts of the
PEP, that would be fine; OTOH if you can e.g put draft code together
in your respective projects, that would be better still :)

-Rob


--
Robert Collins <rbtco...@hp.com>
Distinguished Technologist
HP Converged Cloud

[Aymeric Augustin]

2014-09-20 6:42 GMT+02:00 Russell Keith-Magee <rus...@keith-magee.com>:

Historically, Django hasn't been deeply involved in process of developing WSGI and related standards; this is an opportunity for us to change that trend.

To me the situation is pretty clear.

Either this line will win: https://mail.python.org/pipermail/web-sig/2014-September/005257.html

Then maybe there's a chance we'll end up with a gateway interface that doesn't make every framework undo the transformations performed by the gateway to get back to the HTTP stuff.

Or that line will: https://mail.python.org/pipermail/web-sig/2014-September/005258.html.

Then we'll carry the legacy of PEP 3333 and WSGI will remain the bastard child of CGI that it is and we'll keep doing stuff like value = value.encode(ISO_8859_1).decode(UTF_8) and we'll want to stab ourselves whenever we look at WSGI-related code.

I'll get in touch with Graham. For the record I once started writing a PEP for a better WSGI, then I read web-sig and I carefully archived my draft without telling anyone.

--
Aymeric.

[Ryan Hiebert]

Being the idealist I am, I hope we can find a way to rid ourselves of the pain of cgi. I'd be more than willing to help, but my help would probably be more of a hindrance because of the limited exposure I've had with developing wsgi. However, I did want to register my support to those looking to change things.

Thank you for working on this.

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mXtravDT%2BLhN0-hS9h4uewSGVXqWdEuD-oz%3DLLgSV5%2B1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Collin Anderson]

On Saturday, September 20, 2014 12:25:02 PM UTC-4, Ryan Hiebert wrote:

Being the idealist I am, I hope we can find a way to rid ourselves of the pain of cgi. I'd be more than willing to help, but my help would probably be more of a hindrance because of the limited exposure I've had with developing wsgi. However, I did want to register my support to those looking to change things.

 

I wouldn't mind working with lowercased headers, personally.