This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author demian.brecht
Recipients Lukasa, alex, berker.peksag, brett.cannon, demian.brecht, icordasc, martin.panter
Date 2015-04-03.18:06:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428084368.32.0.506202791157.issue23794@psf.upfronthosting.co.za>
In-reply-to
Content
+1 to the adding the support for HTTP/2. I would personally like to see a few things happen before that though (which I've been putting some effort into as i can)

+ refactor http.client to cleanly separate transport from application protocol level
+ figure out some kind of adapter interface in order to facilitate swapping between 1.1 and 2 (This can start with a clean HTTP/1.1 interface)
+ full HTTP/1.1 support. Given (as i understand it) HTTP/2 is largely an extension of HTTP/1.1 it doesn't make much sense to me to implement the latter before the former.
History
Date User Action Args
2015-04-03 18:06:08demian.brechtsetrecipients: + demian.brecht, brett.cannon, alex, berker.peksag, martin.panter, icordasc, Lukasa
2015-04-03 18:06:08demian.brechtsetmessageid: <1428084368.32.0.506202791157.issue23794@psf.upfronthosting.co.za>
2015-04-03 18:06:08demian.brechtlinkissue23794 messages
2015-04-03 18:06:08demian.brechtcreate