- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Jun 2012 14:07:56 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16738
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 14:07:55 UTC ---
I prefer Option1,since it is a light-weight keep-alive mechanism.
And the generateKeyRequest is used when load the page, but when keep-alive
happens, it does not need reload the page, so we can still use addKey() for
keep-alive.
My question is:
CDM->UA---(keymessage)------>Server
CDM->UA,--ACK----------------Server
In your second comment, it is said that
ACK would be provided via addKey.
What does this mean? ACK from server is provided by addKey() API of UA?
I am a little confused.
(In reply to comment #1)
> In option 1, keymessage would be used to provide the heartbeat, which must be
> ACK'd by the server. The thought is that this ACK would be provided via
> addKey().
>
> While this option seems more sensible for the server and CDM, it is not
> consistent with normal uses of addKey() (and the pairing with
> generateKeyRequest()). Is there a better name for addKey() that addresses both
> use cases? (Assuming we make the change in bug 16548) addKey() is always a
> response to a keymessage event, though one could imagine multiple addKey()
> calls for a given message.)
>
>
> Option 2 is very consistent with the initial key request, but seems overly
> complex for a periodic heartbeat related to the same license.
>
>
> The current text says an "an expiration time or valid duration" should be
> provided in the license. This language seems specific to option 2 and should be
> changed if we choose option 1.
--
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 14:08:05 UTC