HTTP2, one frame at a time
summary
Shows Node's HTTP/2 internals: libuv and TLS termination hand off bytes to the C++ parser dingy http/2, frames multiplex onto streams with credit‑based flow control and priority weights, and header compression uses Huffman coding. Demonstrates using TLS keygen to run a secure localhost server and a live server push that sends bundle.css (background turns hot pink) so the push completes and the pushed resource arrives without an extra request. Experimental flag noted.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:12HTTP/2, one frame at a time
- 2:05The focus of the protocol is on performance; specifically, end-user perceived latency, network and server resource usage.
- 8:38ALPN Negotiations
- 8:57server to confirm upgrade
- 9:09Connection acknowledgement
- 11:39header block gets converted into an octet block (Huffman encoded)
- 13:21multiple streams exist per single connection.
- 14:09connection, endpoints want to prioritize resource allocation
- 15:53Multiplexing streams can cause congestion in a TCP Connection
- 17:23flow-control allows for the receiver to communicate how much load it can handle
- 17:57establishing a connection in node.js
- 20:07server push allows the server to preemptively send data to the client before
- 25:04flow control and better use of TCP connections bring performance gains.
