[Bug 16612] Consider wrapping all encrypted media methods inside a new interface

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16612

Yang Sun <eric.sun@huawei.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eric.sun@huawei.com

--- Comment #3 from Yang Sun <eric.sun@huawei.com> 2012-06-12 05:46:18 UTC ---

Hi, Mark

So this is about encrypted key managed object for media element?
Will generateKeyRequest request browser or request web site?
Why no removeKey method for this interface?

KeySystem means encrypted mechinism used by this media element,right?
The generateKeyRequest will return a key to be used by addkey?

And what's the meaning of cancelKeyRequest? During requesting key from ??? and
we cancel it by a button or js inside logic?

Sorry for so many questions.......

(In reply to comment #0)
> It has been suggested that only a single key manager attribute be added to the
> HTMLMediaElement itself in order to improve encapsulation. For example:
> 
> partial interface HTMLMediaElement {
>     attribute MediaKeyManager keymanager;
> };
> 
> interface MediaKeyManager {
>   void generateKeyRequest(in DOMString keySystem, in Uint8Array? initData);
>   void addKey(in DOMString keySystem, in Uint8Array key, in Uint8Array?
> initData, in DOMString? sessionId);
>   void cancelKeyRequest(in DOMString keySystem, in DOMString? sessionId);
> };

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 12 June 2012 05:46:21 UTC