4 ms·
> Webtransport is designed as a 'QUIC-native' client-server communication protocol to replace websockets. Is there anything wrong with websockets? I thought we
by fractalb 6y ago
> Webtransport is designed as a 'QUIC-native' client-server communication protocol to replace websockets.
Is there anything wrong with websockets? I thought websockets were cool.
- vertex-four 6y agoWebsockets work on HTTP/1.1 (not later versions) and turns the TCP connection into a packet-based transport, unrelated to HTTP. WebTransport works on HTTP/3 and exposes a part of the underlying UDP QUIC connection (while still allowing HTTP/3 messages to travel across the same underlying connection), allowing for stream-based or packet-based subconnections, reliable or unreliable. Basically, it’s a lot more flexible and doesn’t require setting up an entire new connection to work.
- lawl 6y ago> Is there anything wrong with websockets? I thought websockets were cool. I'm excited for the option of having an unreliable connection. Currently you'd need to establish a webrtc data connection to the server, which is a bit cumbersome when you really don't need or want the rest of webrtc.
- Andrex 6y agoWebSockets are not cool if you ask anybody who's worked with them in gaming. :)