- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Dec 2013 23:54:09 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23955
Adrian Bateman [MSFT] <adrianba@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |adrianba@microsoft.com
--- Comment #3 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
(In reply to Joe Steele from comment #1)
> What is the workflow you are proposing for loading previously loaded keys
> then? Would the application have to keep track of each sessionID it has seen
> and then try to load them later? I am not sure how this is intended to solve
> the general problem of CDM data storage. Is that the intent?
The proposal for loadSession implies that CDMs will be able to store keys
between browsing sessions. Calling loadSession with a sessionID that would be
stored locally in some JavaScript enabled mechanism (e.g. localstorage or
IndexedDB) would ask the CDM to reconstitute the MediaKeySession from whatever
it stored.
I think this means that the goal of avoiding general CDM data storage has been
dropped.
I think this is a good approach. The implementation of the method is optional
(not the method itself) - it will throw if this isn't supported by the CDM.
Assigning to David.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 12 December 2013 23:54:11 UTC