WebTransport and its place among other protocols
summary
Overview of WebTransport: what it is, why it was created, and how it compares to existing protocols. Covers current W3C draft status and includes a hands-on demo of the WebTransport API and steps to set up a local environment for testing.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:27Organizational details
- 2:34Introduction
- 3:16Motivation for WebTransport
- 5:06HTTP versions compared
- 7:38HTTP/2 limitations
- 9:05HTTP/3 vs QUIC differences
- 10:54QUIC security benefits
- 13:06Mobile networks and HTTP/3
- 14:12WebSocket TCP limits
- 15:36WebRTC protocol issues
- 17:21WebTransport new standard
- 17:45WebTransport features
- 18:52WebTransport modes
- 21:06WebTransport status timeline
- 22:29QUIC/HTTP/3 implementation
- 23:11Browser support
- 24:38WebTransport demo
- 25:20Server setup
- 27:27Code structure
- 29:13Running tests
- 31:48Dev tools analysis
- 32:522023 roadmap
- 34:22WebTransport future
- 35:03Q&A
related talks
44mWebTransport: When and How to Use It?
40mTransport and Ajax
42mHTTP/3 and UDP Protocols for Client and Server Online Game Development
30mThere and back again: reinventing UDP streaming with QUIC
36mStreaming over the web with modern Ruby
21mReplacing WebRTC with Media over QUIC
44mApplication‑Level Protocols in the Browser
46mHTTP/3: 37 Years of the HTTP Protocol