HTTP 2.0: why and how
summary
HTTP/2 replaces text with a binary framing layer and adds multiplexed streams, HPACK header compression and server push so one TCP connection can carry hundreds of concurrent requests (demo uses 24 pushed images) and eliminate dozens of round trips (example page had 215 requests, 9 MB). Browsers require TLS for HTTP/2; Java stacks already support it (Jetty 9.4, Tomcat backports, JDK9 incubator client, servlet push APIs). Real-world caveats: browser implementation differences, worse behavior under packet loss, and QUIC as an emerging UDP alternative.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:14Human Web Interaction
- 5:52Faster Website Mean More Money
- 13:22Header Compression
- 15:08Hb 2 Push
- 17:22Push Cache
- 33:34Jdk 8 Is Required
- 35:02The Bad News about Hp 2
- 41:18Conclusion
