Comment #6 on issue 16013 by [email protected]: Implement sparse
caching for audio/video resource loading
http://code.google.com/p/chromium/issues/detail?id=16013
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=27587
------------------------------------------------------------------------
r27587 | [email protected] | 2009-09-29 19:46:29 -0700 (Tue, 29 Sep 2009)
| 22 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/webkit/glue/media/buffered_data_source.cc?r1=27587&r2=27586
M
http://src.chromium.org/viewvc/chrome/trunk/src/webkit/glue/media/buffered_data_source.h?r1=27587&r2=27586
M
http://src.chromium.org/viewvc/chrome/trunk/src/webkit/glue/media/buffered_data_source_unittest.cc?r1=27587&r2=27586
Change 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.
Review URL: http://codereview.chromium.org/248012
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
