4 ms·
Parallel requests are nice, but is there a standard way to request larger files sequentially (explicitly wanting nicely pipelined head-of-line-blocking delivery
by kaetemi 5y ago
Parallel requests are nice, but is there a standard way to request larger files sequentially (explicitly wanting nicely pipelined head-of-line-blocking delivery)? Think streaming media, where you want chunks to arrive one after the other, without the second chunk hogging bandwidth while the first one is still downloading too.
- johncolanduoni 5y agoAFAIK HTTP/3 doesn’t send data out-of-order within a single stream any more than TCP does. So if you want a large file to be streamed with head-of-line blocking you just don’t send multiple range requests for it.
- kaetemi 5y agoWhat I want is multiple large files (chunks being individual files in a stream) to arrive one after the other, without re-request gap, and without multiple files hogging bandwidth. (i.e. HTTP/1.1 Pipelining) It's easy with streaming video, when you can just time the requests at a fixed rate. But for stuff like streaming game assets, you never know how long each download will take. Doing parallel requests will just slow down the time for the first asset to appear, and doesn't guarantee that you fill the bandwidth anyway if the latency is high enough...