3 ms·
> HTTP 3 should have been split into three: a file access protocol, a arbitrary TCP like pipe and a metadata channel HTTP3 is basically just HTTP2 on top of QU
by ninkendo 2y ago
> HTTP 3 should have been split into three: a file access protocol, a arbitrary TCP like pipe and a metadata channel
HTTP3 is basically just HTTP2 on top of QUIC… so you already have the tcp-like pipe, it’s called QUIC. And there’s no reason to have a metadata channel when there are already arbitrary separate channels in QUIC itself.
- KaiserPro 2y agoYou're right of course, it has virtual channels. I just think it would have been good to break with the old HTTP semantics and change to something reflecting modern usage.