[Bug 19809] Specify which portion of addKey() algorithm to run when updating license for a key

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

David Dorwin <ddorwin@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from David Dorwin <ddorwin@google.com> ---
(In reply to David Dorwin from comment #5)
...
> I'm leaning towards deleting the key storage algorithm and noting that it is
> CDM specific. I think overlapping keys should not be deleted such that when
> one session is closed, an overlapped key in another session is available.
Changeset https://dvcs.w3.org/hg/html-media/rev/6b1b0aa1415c removes the key
storage algorithm and adds non-normative text about CDM behavior related to
keys and sessions.

...
> There may be cases where no new key is stored (as in the current algorithm)
> but playback becomes possible. Given this and the possible removal of the
> key storage algorithm, we may want to remove "did store key" and always try
> to resume playback when waiting for a key.
Changeset https://dvcs.w3.org/hg/html-media/rev/6b1b0aa1415c removes "did store
key" and changes the algorithm to always attempt to resume playback when
waiting for a key unless an error occurred.

> Finally, |key| is a misleading and inappropriate name for update()'s
> parameter. We should rename it. I can file a separate bug, but this is a
> good context to be thinking about that as well.

Changeset https://dvcs.w3.org/hg/html-media/rev/cf1786f8f616 renames |key| to
|response|. We can iterate on the name, but this at least removes the
confusion.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 5 November 2013 23:53:21 UTC