- From: Sunyang (Eric) <eric.sun@huawei.com>
- Date: Thu, 6 Sep 2012 08:59:27 +0000
- To: Mark Watson <watsonm@netflix.com>, "<public-html-media@w3.org>" <public-html-media@w3.org>
Thanks for the solution. But why we need retrieve a "released" MediaKeySession£¬ then fire event on it? Yang Huawei > -----Original Message----- > From: Mark Watson [mailto:watsonm@netflix.com] > Sent: Tuesday, September 04, 2012 10:22 PM > To: <public-html-media@w3.org> > Subject: ACTION-5: key release > > http://www.w3.org/html/wg/media/track/actions/5 > > All, > > The status of this action is that I have provided a proposal as a comment to > the bug [1]. For ease of reference I've copied the proposal here, but please > make comments in the bug, or on the call today. > > ”Mark > > If key release is supported, then > (i) when the MediaKeySession.close() method is called, the session enters a > "key release pending" state and a keymessage event is fired on the > MediaKeySession, containing the key release object > (ii) when the application receives the key release acknowledgement from the > server the session is updated with this message using the addKey() method > (or > update(), if we rename it as per bug 18531 [2]). The MediaKeySession enters > a > "key release complete" state > (iii) a new method is added to MediaKeys: MediaKeySession? > retrieveClosedSession() which will retrieve a MediaKeySession object in the > key > release pending state. Subsequent calls to this method will retrieve further > sessions in the 'key release pending state' until none are left (we could > consider returning a list of MediaKeySession objects). A keymessage event is > fired on each MediaKeySession retrieved with this method containing the key > release object. > > [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17199 > [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=18531
Received on Thursday, 6 September 2012 09:01:23 UTC