[Bug 26575] Separate creation of the MediaKeySession from "message" event generation

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

David Dorwin <ddorwin@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #10 from David Dorwin <ddorwin@google.com> ---
https://dvcs.w3.org/hg/html-media/rev/19ef12173afb (along with the
uninteresting https://dvcs.w3.org/hg/html-media/rev/ec33087ef0db) implements
something close to the proposal in comment #1. The primary differences are
createSession() is still asynchronous (see below) and generateRequest() instead
of generateLicenseRequest().

The IDL is as follows:

MediaKeys
 Promise<MediaKeySession> createSession(optional SessionType sessionType =
"temporary");

MediaKeySession
 Promise<void> generateRequest(DOMString initDataType, (ArrayBuffer or
ArrayBufferView) initData);
 Promise<bool> load(DOMString sessionId);

Note the return types. load()'s bool indicates whether the session was found,
since not found is not a rejectable condition.


createSession() still asynchronously returns the MediaKeySession in a promise,
but I think we can probably make it synchronous since it does not really do
anything or touch the CDM (see the algorithm). Does anyone see a reason not to
make it synchronous as proposed in comment #1?
 MediaKeySession createSession(optional SessionType sessionType = "temporary");


The algorithms have to track both the uninitialized state (neither
generateRequest() nor load() has been called) and callable state
generateRequest() or load() has completed successfully).

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

Received on Monday, 25 August 2014 18:47:43 UTC