- From: <bugzilla@jessica.w3.org>
- Date: Tue, 29 Apr 2014 22:11:32 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25218 --- Comment #10 from Mark Watson <watsonm@netflix.com> --- Joe: there is one more option, that sessions contain content keys but they are not constrained only to contain content keys. It is just that content keys are the only kind that are visible in a keysystem-independent way on out API. So there can be other state in the session besides content keys. There can also be state that CDM maintains which is not part of any session. A message back from a license server can contain whatever the CDM needs to derive the content keys. This may include chains of keys or information that populates state outside the session (though, preferably, scoped within the origin). Persisting the session would persist any other information the CDM has in that session. Releasing the session would release it. But releasing the session need not release all information which came from the license server, if some of that relates to some keysystem-specific scope which is outside any session, for example a domain. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 29 April 2014 22:11:37 UTC