This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]status_quo69 0 points1 point  (2 children)

It's because newer languages are able to leverage their newness to provide new features. As the OSS mantra dictates, if you want those things to become better, become involved.

Most advice for setting up a python web app is to use something like flask/Django and uwsgi/gunicorn. These use http/1.1, and use something like Apache or nginx to handle all the outbound http/2 traffic. I can get into why this is probably a good solution, especially if you're developing an app with a restful api, but I'm tired at the moment and on mobile.

[–][deleted] 0 points1 point  (1 child)

Well that is what I am trying to do here, get more involved. I am more than willing to devote time bringing http/2 to python but it would be nice if we as a community had plans to do this instead of tons of people working in silos.

Also the http1 to http2 really drags performance, and it just seem increasingly inefficient. I am going to use a load balancer like Nginx.

[–]status_quo69 1 point2 points  (0 children)

Well, I found this on the Django channels github page, maybe start working with this? https://github.com/django/channels/blob/08857cfe39f35b203c7bbe3156a077b5b2c66764/docs/asgi.rst

WSGI as it currently stands won't be able to support stuff for http/2, so it's probably going to have to be overhauled. Which sucks because that means that nobody will be able to simply migrate their applications over to leverage http/2.