3 ms·

> What an odd way of phrasing it. It should be, "The next major version of HTTP, HTTP/3, will be QUIC” No? Http/3 is one application of quic, but sits on top

> What an odd way of phrasing it. It should be, "The next major version of HTTP, HTTP/3, will be QUIC” No? Http/3 is one application of quic, but sits on top of it. That’s why it has a separate RFC, which explains that: > While delegating stream lifetime and flow-control issues to QUIC, a binary framing similar to the HTTP/2 framing is used on each stream. Some HTTP/2 features are subsumed by QUIC, while other features are implemented atop QUIC. While google did design QUIC with HTTP in mind, you can use QUIC for other protocols e.g. Microsoft has shipped SMB on QUIC in Windows Server 2022. MS also supports direct QUIC uses on Xbox Series consoles and has a guide to use MsQuic with the GDK.

iforgotpassword 4y ago
> MS also supports direct QUIC uses on Xbox Series consoles This is so fucking ridiculous. Tried writing my first android app a few months ago, and for reasons wanted to do QUIC. I was absolutely sure this was going to be a no-brainer, as Google more or less being the inventor of it, or at least a very strong proponent, must have made quic a first class citizen of Android and its SDK years ago now. I mean, all their apps use it. Imagine how much in disbelief I was when I learned there is nothing available, except a library that wraps Chrome's network engine and let's you use http3 over quic, but not quic directly. You'd have to fiddle with using a 3rd party native lib and some bindings and whatnot, so I just deleted Android studio and went for a walk. Yes I'm still bitter.