3 ms·
Meanwhile fast.com (and presumably netflix cdn) is using http 1.1 still.
by ec109685 2y ago
Meanwhile fast.com (and presumably netflix cdn) is using http 1.1 still.
- dan-robertson 2y agoWhy do you need multiplexing when you are only downloading one (video) stream? Are there any features of http/2 that would benefit the Netflix use case?
- jeltz 2y agoQUIC handles packet loss better. But I do not think there is any benefit from HTTP2.
- dan-robertson 2y agoYeah I was thinking the same thing – in some video contexts with some video codecs you may care more about latency and may be able to get a video codec that can cope with packet loss instead of requiring retransmission – except it seemed it wouldn’t apply too much to Netflix where the latency requirement is lower and so retransmission ought to be fine. Maybe one advantage of HTTP/3 would be handling ip changes but I’m not sure this matters much because you can already resume downloads fine in HTTP/1.1 if the server supports range requests (which it very likely does for video)
- yencabulator 2y agoMost significantly, QUIC handles packet loss in a way that is fair to all the contained streams; no head-of-line blocking. But the parent asks > Why do you need multiplexing when you are only downloading one (video) stream? So that largely doesn't apply.