Re: HTTP/2 and WSGI
2014-09-20 6:42 GMT+02:00 Russell Keith-Magee : > > 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 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. -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@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.
Re: HTTP/2 and WSGI
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 > On Sep 20, 2014, at 2:34 AM, Aymeric Augustin > wrote: > > 2014-09-20 6:42 GMT+02:00 Russell Keith-Magee : >> >> 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 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. > -- > 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-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@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. -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@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/29FFE9AA-823C-4D5F-94A7-D86537157E43%40ryanhiebert.com. For more options, visit https://groups.google.com/d/optout.
Re: HTTP/2 and WSGI
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. -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@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/a69ff944-8fbf-44eb-bcb3-5abc59be5f85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.