![](https://secure.gravatar.com/avatar/3041a99ff2b84bc3dc10805020d35516.jpg?s=120&d=mm&r=g)
2016-08-08 13:24 GMT+02:00 Cory Benfield <cory@lukasa.co.uk>:
On 8 Aug 2016, at 11:16, Ludovic Gasc <gmludo@gmail.com> wrote:
Certainly some protocols/transports should be easier to have this split than others: Interesting to know if somebody has already tried to have QUIC and HTTP/2 in the same time with Python.
AFAIK they haven’t. This is partly because there’s no good QUIC implementation to bind from Python at this time. Chromium’s QUIC library requires a giant pool of custom C++ to bind it appropriately, and Go’s implementation includes a gigantic runtime and is quite large.
I had the same conclusion. For now, I don't know what's the most complex: Try to do a Python binding or reimplement QUIC in Python ;-)
As and when a good OSS QUIC library starts to surface, I’ll be able to answer this question more effectively. But I’m not expecting a huge issue. =)
We'll see when it will happen ;-) Implemented in 2012, pushed on production by Google in 2013, and 3 years later, only one Web browser and one programming language have the support, to my knowledge. Nobody uses that except Google, or everybody already migrated on Go ? ;-) Or simply, it's too much complicated to use/debug/... ?