Check: HTTP/2 header compression and gateways

Knowledge check · self-test
Check: HTTP/2 header compression and gateways
Review HPACK state, connection reuse, and the sequential 50-sensor baseline.
Review HPACK state, connection reuse, and the sequential 50-sensor baseline.
Checkpoint: header compression {.depth-l0}
You now know:
- HPACK sends full repeated headers once, then reuses index references around 15-30 bytes instead of retransmitting about 350 bytes.
- HPACK header compression matters most when a gateway repeatedly sends the same `Host`, `Authorization`, and `Content-Type` fields; the reduction depends on the header mix.
- Header compression only pays off when the connection stays alive long enough for the shared table to be reused.
:::::: {.callout-tip}
##
Checkpoint: multiplexed gateways {.depth-l0}
You now know:
- HTTP/1.1 can force 50 sequential requests or multiple connection waves; HTTP/2 sends the same gateway batch over one multiplexed connection.
- The chapter's gateway example compresses the delay from about 10 seconds to about 200 ms when the cloud API can keep one HTTP/2 session open.
- HTTP/2 is a gateway and cloud-integration tool, not a replacement for MQTT or CoAP on the smallest sensors.
:::Back to Modern HTTP: HTTP/2, HTTP/3, and Selection: Back to HTTP/2 and HTTP/3