[Bug 20688] Provide more details on when keyadded should be fired

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

--- Comment #2 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
We discussed this on the call in February:
http://www.w3.org/2013/02/05-html-media-minutes.html

The original mental model I had for the session events is as follows:

1) The application has initData, either from needKey or otherwise determined by
the application.

2) The applications calls createSession and passes the initdata.

3) The UA fires keymessage and provides the message data that the application
sends to a license service.

4) The license service sends back a response, which is passed to the UA with
the update() method.

5) The UA may now either go back to step 3 and fire another keymessage, or fire
keyadded to indicate that the session process has halted.

This is related to bug 19208, which talks about potentially not firing
keymessage. If we did that, we would need keyadded (or something with a
different name) to indicate that the session negotiation was done.

Since the February discussion, we have also discussed that CDMs may be
initialized asynchronously and the first opportunity for indicating an error is
keyerror when a session is created. We may need an additional event to indicate
that the session has started following the pattern of progress events.

The description above is not what the spec currently describes. We could change
to this model and perhaps rename keyadded to sessionloaded or similar.

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

Received on Tuesday, 23 April 2013 17:03:06 UTC