Prerequisite: the visual tour. Complete the stream lab before the flow-control and QPACK cards. Outcome: connect each mechanism to an application problem and explain its limits.

​
Rotate the concept deck

Drag or swipe the carousel to turn it. You can also select a numbered card or use the arrow keys. List view shows all card titles without perspective. Pick a card selects a different topic for a quick review. The deck never rotates automatically.
Open the carousel in a separate page. Without JavaScript, the separate page shows all 15 explanations in order.

​
Choose a route through the cards

Each card contains an original diagram, a concrete example, a question, and an explained answer. The diagrams describe mechanisms. The page does not probe a server, perform a security audit, or predict throughput.

​
Practice explaining a card

  1. Select a card and read its example.
  2. Answer its question before opening the explanation.
  3. Identify one limit or prerequisite for the mechanism.
  4. Describe where the mechanism affects a video stream, a sensor update, or a file transfer.
  5. Open the source link when you need the exact protocol rules.
Completion check: explain why QPACK can make a response wait even when its QUIC stream has no missing bytes. Then explain why adding streams does not create more network capacity.

​
Reference status

The deck distinguishes baseline QUIC from extensions and application protocols. It does not claim that our SDK implements every card. References checked on 2026-09-20: Each card links to its own primary specification. Check endpoint support before applying an extension in a real system.

​
Presentation credit

The 15-topic selection and rotating-card presentation take inspiration from PosTQuic. The academy uses original code, diagrams, scenarios, and answers. Return to packet structure and handshakes for packet fields and calculations.