[Bug 17750] Define the behavior MediaKeySession close() and clearing the keys attribute

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

--- Comment #16 from David Dorwin <ddorwin@google.com> ---
It seems likely that use cases involving stored sessions will want to use
close() to indicate that the stored session should be removed from local
storage.

In that case, close() is more than a hint to destroy in-memory keys and move
the session to the CLOSED state. I think it's fine for close() to be a "hint",
but we might want the name to give an indication that it is more than just a
quick way to move a MediaKeySession to the CLOSED state. It's is really
permanently releasing the backing resources for the session.

Maybe it should be called release() or something similar (free() and destroy()
come to mind but don't seem to fit all cases as well).

Note: When using stored session data, apps would not be able to use close()
just to accelerate closing of a MediaKeySession. That scenario probably doesn't
make much sense anyway since the session is stored locally.

An alternative is to add an explicit method (e.g. release()) in addition to
close(). This has the advantage of there being no ambiguity in the behavior,
but it adds another method to EME that may not always be useful.

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

Received on Tuesday, 5 November 2013 00:54:11 UTC