- From: <bugzilla@jessica.w3.org>
- Date: Fri, 23 Sep 2011 03:13:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14109
Offbeatmammal <offbeatmammal@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |offbeatmammal@gmail.com
--- Comment #5 from Offbeatmammal <offbeatmammal@gmail.com> 2011-09-23 03:13:00 UTC ---
this is something that hopefully DASH will help with in the future (as Smooth
Streaming, HLS and the other fMPEG implementation do today) by taking advantage
of small fragments, multiple bitrates and tuneable heuristics - allowing a site
to (for instance) make a determination for their player to only download a
certain number of fragments / %age of file / minutes of content if (for
instance) the user switches away from the window
the current <video> implementation could make the same decision and encode
logic to suspend download of further content once the canplaythrough status has
been reached (even though the content has not yet been delivered) and rely on
the bandwidth remaining consistent enough that when the user switches focus
back and hits play again then the remaining delivery portion will complete
without causing buffering
Something like http://www.w3.org/Bugs/Public/show_bug.cgi?id=14186 would add
further support for this allowing the developer to make informed decisions
based on returned http response codes and additional meta information
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 23 September 2011 03:13:03 UTC