- From: <bugzilla@jessica.w3.org>
- Date: Tue, 29 Apr 2014 22:25:48 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25218 --- Comment #12 from Mark Watson <watsonm@netflix.com> --- (In reply to David Dorwin from comment #11) > (In reply to Mark Watson from comment #10) > That really eliminates any hopes of interoperability or expected behavior > for the application. Also, if some of the state is not visible to the > application, how can the application (or anyone) manage it? The application doesn't need to manage it. The keysystem is managing it between client and server component. I should say that my understanding is that any additional state is really just an optimization. We should assume that a CDM in a 'cold state' can always perform the necessary message exchanges with its server peer to get the content keys needed to decrypt the content. What I understood Joe was asking for was to avoid repeating exchanges every time when they can be done once and the resulting state persisted. The application doesn't even need to know this is happening. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 29 April 2014 22:25:49 UTC