6 ms·
Does streaming compression work if some packets are lost or arrive in a different order? Seems like the compression context may end up different on the encoding
by lambdaloop 9mo ago
Does streaming compression work if some packets are lost or arrive in a different order? Seems like the compression context may end up different on the encoding/decoding side.. or is that handled somehow?
- duskwuff 9mo agoIt sounds as though the data is being transferred over HTTP, so packet loss/reordering is all handled by TCP.
- dgoldstein0 9mo agoYes, or by http3's in order guarantees on the individual streams (as http3 is udp)
- dgoldstein0 9mo agoI think the underlying protocol would have to guarantee in order delivery - either via tcp (for http1, 2, or spdy), or in http3, within a single stream.
- gkbrk 9mo agoWebSockets [1] run over TCP, and the messages are ordered. There is RFC 9220 [2] that makes WebSockets go over QUIC (which is UDP-based). But that's still expected to expose a stream of bytes to the WebSocket, which still keeps the ordering guarantee. [1]: https://datatracker.ietf.org/doc/html/rfc6455 https://datatracker.ietf.org/doc/html/rfc6455 [2]: https://datatracker.ietf.org/doc/rfc9220/ https://datatracker.ietf.org/doc/rfc9220/