3 ms·
There is still a place for WebSockets in HTTP/2. The fairly recent RFC 8441 defines a mechanism to reserve a single HTTP/2 stream for bidirectional WebSockets.
by lucaspardue 8y ago
There is still a place for WebSockets in HTTP/2. The fairly recent RFC 8441 defines a mechanism to reserve a single HTTP/2 stream for bidirectional WebSockets.
It is feasible for a similar mechanism for also work for HTTP/3, just no-one has gone to the effort yet.
https://tools.ietf.org/html/rfc8441 https://tools.ietf.org/html/rfc8441
- seabrookmx 8y agoThanks, this is basically what I was looking for. With quic I'm guessing you could have multiple Websocket and http3 streams within one connection and have them not block eachother on packet loss, which is pretty neat.