- From: <bugzilla@jessica.w3.org>
- Date: Fri, 25 May 2012 22:52:36 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16738
David Dorwin <ddorwin@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
--- Comment #1 from David Dorwin <ddorwin@google.com> 2012-05-25 22:52:35 UTC ---
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 Friday, 25 May 2012 22:52:38 UTC