- From: <bugzilla@jessica.w3.org>
- Date: Thu, 01 May 2014 23:56:32 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25218 --- Comment #23 from Joe Steele <steele@adobe.com> --- I just had a long discussion on this topic with the other engineer at Adobe who will be implementing this. He agrees with me that sessions are not the right level of granularity, but has convinced me that keys are not either since a license can contain multiple keys used for a stream. I am thinking this bug should be RESOLVED to LATER, unless we can agree on a definition of license to use as a reference point. The problem of loadSession/release remains. Here is how our implementation will behave for loadSession(): Our CDM can support it - but it is completely irrelevant. If licenses are cacheable, the CDM will cache them and retrieve them based on the initData. So this would either behave the same as createSession or just reject the Promise. Haven't decided yet. Here is how our implementation will behave for release(): Our CDM will release only content keys, and ignore any non-content keys. Those are not releasable. It sounds like both of these behaviors are acceptable based on your comments above. I will probably open another bug to remove loadSession() since (a) it is not clear to me now why this is needed to support the basic use case and (b) it muddies the waters for supporting future use cases like offline playback. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 1 May 2014 23:56:33 UTC