Chromium Code Reviews
DescriptionChange how <video> fetch a resource to make it friendly to sparse caching
BUG=16013
TEST=test_shell_tests --gtest_filter=Buffered*
Also video on a server that doesn't support range request will still work.
How <video> used to fetch a resource:
1. Fetch the whole file to get the header
2. Fetch a small range (1, 1) to determine if server supports range request
3. If [2] was successful, then fetch the file with range request if necessary
If [2] failed, prevent range request by telling ffmpeg this is streaming
New way of fetching a resource for <video>:
1. Fetch (0, 1023) to get the header (This needs more experiment).
2. If [1] was successful, then request later on will be made partial
If [1] failed, prevent range request by telling ffmpeg this is streaming
By doing this change we can eliminate one request before we can start the
file. And with the help of sparse cache, we would be able to reuse the first
1KB fetched even we need to fetch the index at the end of file.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=27587
Patch Set 1 #
Total comments: 16
Patch Set 2 : style #
Total comments: 6
Messages
Total messages: 4 (0 generated)
|
|||||||||||||||||||||||||||||||||||||