HTTP 2.0 and QUIC - protocols of the (near) future
summary
Claims that HTTP 2.0 brings binary multiplexed streams, header compression and server push and that QUIC (over UDP) adds zero round trip time reconnects and no head‑of‑line blocking. Builds a test site HTTPRulez.com, serves via NodeJS with ALPN, measures with WebPageTest and Chrome Canary, sees a single multiplexed connection replacing one connection instead of six and shorter waterfalls. QUIC endpoint is not yet in production so QUIC results are projected not deployed; transcript cites 80–90 requests for top sites and QUIC vs TCP+TLS RTT examples (0ms vs 200ms repeat).
AI-written summary · about
chapters (8)
- 0:00Start
- 0:46Why Do We Need a New Version of Http Protocol
- 3:45Http Pipelining
- 10:01Server Push
- 13:00Priorities
- 13:34Dependencies
- 14:07Headers
- 21:39Forward Error Correction
related talks
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
30mQUIC, in Theory and Practice
51mHTTP/2 & Quic - Teaching Good Protocols to Do Bad Things
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
40mHTTP/3 - HTTP over QUIC is the next generation
01h 00mHTTP/2 - The future of the web today
51mDown the line: Evolving HTTP and making things QUIC
19mThe Future With QUIC