Senior LevelHTML & Semantic Web
How do HTTP/2 and HTTP/3 multiplexing change HTML asset loading strategies?
❓ Interview Prompt: Explain HTTP/2 multiplexing, QUIC protocol in HTTP/3, single TCP connection reuse, and domain sharding antipatterns.
In HTTP/1.1, browsers were limited to 6 concurrent TCP connections per domain, requiring techniques like asset concatenation and domain sharding (cdn1, cdn2).
HTTP/2 & HTTP/3 Modern Strategy:
•
Multiplexing: Transfers dozens of files concurrently over a single TCP/QUIC connection without head-of-line blocking.
•
Antipattern Removal: Domain sharding and massive CSS/JS file bundling are now antipatterns! Deliver smaller modular ES modules directly over HTTP/2/3.
Code Implementation Example
html
<!-- HTTP/2 / HTTP/3 fetches multiple modular ES modules over 1 connection -->
<script type="module" src="/js/utils.js"></script>
<script type="module" src="/js/auth.js"></script>
<script type="module" src="/js/app.js"></script>💡Loading modular ES modules over HTTP/2 multiplexed connections.
🎯 Interview Key Takeaway
Avoid domain sharding in HTTP/2/3 environments; multiplex smaller modular assets over a single connection.
#HTTP/2#HTTP/3#Multiplexing#Performance#Senior
Back to all HTML & Semantic Web Questions→