3 ms·
It doesn't define high level semantics other such as QUIC can use or build from. It's the whole kit and caboodle when it should have been broken up into clean
by rektide 13y ago
It doesn't define high level semantics other such as QUIC can use or build from.
It's the whole kit and caboodle when it should have been broken up into clean modular pieces: framing layers, protocol layers, semantic layers. QUIC or other hopefuls trying to break from the mobile-horror-show that is TCP are left with nothing to start from, and HTTP/2 docs devolve into a commingled big-ball-of-mud as it hops from low level aspects to higher level aspects.
- M2Ys4U 13y agoHTTP/2 doesn't prevent us from using lower-level protocols like QUIC, though. HTTP/2 over QUIC would work just as HTTP/2 over TCP