- From: <bugzilla@jessica.w3.org>
- Date: Thu, 17 May 2012 20:32:46 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17004
Kevin Streeter <kstreete@adobe.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kstreete@adobe.com
--- Comment #1 from Kevin Streeter <kstreete@adobe.com> 2012-05-17 20:32:45 UTC ---
Here is a list of some of the issues/use cases I feel we should verify as part
of adding this functionality. They are listed in no particular order:
* Content Initialization: not only is the timeline discontinuous, but the new
media will likely require initialization (like H264 SPS/PPS).
* Seeking: the effective mapping for the stream timeline needs to be completely
deterministic (from the app script's perspective), so that a sane view of the
total stream timeline can be computed for things like seeking.
* Tracking: this is related to the seeking requirement...not only does the
script need to be able to compute the timeline for seeking, but it also needs
to be able to infer where in the the sequence the current playhead is
("tracking" the playhead).
* Content Protection: this behavior will likely impact the content protection
proposal, in that we should be able to change DRM key/license context at the
discontinuous content boundaries. This may mean a new key/license, or a shift
from protected to unprotected (and back to protected).
This is everything I can think of now :)
--
Configure bugmail: https://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 Thursday, 17 May 2012 20:32:52 UTC