A quick primer on http2
summary
HTTP/2 replaces text with binary frames and multiplexes many streams over a single TCP connection so handshakes and connection overhead disappear; the RFC grows from ~170 pages to ~400 and the draft sits at draft‑17 expiring in August. It uses HPACK header compression, per‑stream flow control, stream dependency/priority and server push_promise to reduce latency (80 asset page example). Adoption shows browsers and CDNs supporting it while nginx/apache hold back; try ng http i or Apache Traffic Server as an HTTP/2 endpoint.
AI-written summary · about
