Ch. 20 · Networking

HTTP Multiplexing and Transport Trade-Offs

HTTP Multiplexing and Transport Trade-Offs. Learn the reasoning, a practical example, common mistakes and an interview exercise.

~2 min readadvancedupdated Oct 3, 2026

Multiplexing allows multiple logical requests to share a connection. Transport and protocol details still affect contention and loss behavior.

Before you start

You should understand clients, servers, IP addresses and ports. Follow a request through name resolution, connection establishment and application exchange. Distinguish protocol guarantees from deployment policy, and use observations from the relevant layer rather than guessing from one browser error message.

The practical goal is to reason through this situation: HTTP/2 streams share a TCP connection; HTTP/3 uses QUIC transport. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.

Step-by-step walkthrough

Step 1: Separate logical and physical transport

Multiple streams share resources under protocol rules.

Step 2: Inspect loss and contention

HTTP/2’s streams share TCP behavior; HTTP/3 uses QUIC.

Step 3: Measure complete performance

Server capacity and bandwidth still limit useful throughput.

Worked scenario

HTTP/2 streams share a TCP connection; HTTP/3 uses QUIC transport.

A page issues many independent resources over one HTTP/2 connection. Multiplexing reduces some connection-management costs but does not make a slow server compute faster. Packet loss and prioritization can still affect delivery. Compare setup, transfer and processing evidence rather than assuming the newer protocol guarantees a faster page.

Common mistake

Multiplexing does not make server work or bandwidth unlimited.

Verify the behavior

Measure representative page loading under both good and impaired network conditions.

Interview exercise

Explain a slow multi-request page.

Answer and reasoning

Measure prioritization, server capacity, connection setup and transfer loss instead of assuming the protocol version guarantees speed.

Continue learning

Compare the scenario with the Networking interview questions and test your understanding with the Networking MCQs. For terminology and implementation details, consult the reference material.

More in Networking

read ✓Networking · mid

Networking: DNS Caching and TTL

Understand positive and negative caching, why changes are not instant, and how TTL trades propagation speed against query load.

~2 min readread →
read ✓Networking · easy

Networking: DNS Record Types

Read and choose DNS records: A and AAAA for addresses, CNAME for aliases, and MX and TXT for mail and verification.

~2 min readread →
read ✓Networking · mid

Networking: HTTP Redirects

Choose between 301, 302, 307 and 308, know which preserve the request method, and avoid caching and loop mistakes.

~2 min readread →
esc