HTTP/3 and UDP Protocols for Client and Server Online Game Development
summary
Coverage of networking options for real-time browser games, comparing TCP-based approaches and newer UDP/QUIC-based ones (HTTP/3, WebTransport). Describes browser limitations versus native platforms, explains differences between TCP and UDP, and presents a demo and benchmarks of an online game using both protocols. Technologies mentioned: JavaScript game client (Haxe, Heaps.io, WebTransport) and TypeScript backend (NestJS, Socket.IO, WebTransport).
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:27Speaker intro
- 3:13Online game protocols
- 4:36TCP vs UDP in games
- 7:46WebRTC in gaming
- 9:09HTTP/3 history
- 10:35HTTP/3 features
- 12:28HTTP/2 to HTTP/3
- 13:12HTTP/3 speed
- 14:14HTTP/3 browser support
- 15:26Check HTTP/3 support
- 16:51HTTP/3 self-signed cert
- 19:00HTTP/3 in Node.js/Deno
- 20:24WebTransport vs WebSocket
- 21:10WebTransport streams
- 24:03Create WebTransport object
- 26:53Game loop demo
- 30:08WebTransport test results
- 30:31HTTP/3 & WebTransport demo
- 33:05Conclusions
- 35:18Q&A
related talks
13mSimulimi i UDP ne Web duke përdorur WebRTC
46mHTTP/3: It's all about the transport!
37mHTTP/3: why and where are we?
40mHTTP/3 - HTTP over QUIC is the next generation
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
30mHTTP/3 where are we now? State of the art in our servers.
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
30mThere and back again: reinventing UDP streaming with QUIC
