2 ms·
> You've basically described what QUIC is in this paragraph You would need kernel support here, though, would you not? (And you would need a generic protocol.
by deathanatos 8y ago
> You've basically described what QUIC is in this paragraph
You would need kernel support here, though, would you not? (And you would need a generic protocol. I have admittedly not studied QUIC thoroughly yet, but my impression was that it was strictly HTTP / not generic.) Without kernel support and/or being generic, I don't see how it's really different from HTTP/2 w/ a single TCP connection.
- tialaramex 8y agoQUIC is a general protocol, it's just that the only significant customer for the fancy features today is HTTP. Speaking QUIC means accepting a non-trivial connection refusal rate (for HTTP you fall back to HTTP/2 or 1.1) because some corporates block it, so if you don't want the extra features you probably wouldn't want QUIC. This document is about doing HTTP on QUIC, so it's renaming itself HTTP/3, the main QUIC document is as you've described it 'generic'