[Bug 21854] Define MediaKeySession life cycle states and/or events

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

--- Comment #9 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
Our proposal is to have session state as shown in the attached state transition
diagram.

A session will start in the CREATED state. A keyerror event might fire taking
the session to the ERROR state. Alternatively a keyready event might fire
taking the session to the READY state. READY means that the session does not
expect to block playback if encrypted content is encountered.

During key acquisition, the session moves to the PENDING state when a
keymessage event fires. PENDING means that if encrypted content is encountered
that needs the key or keys being acquired in this session then playback will
stall. Zero or more keymessage events might fire while in the PENDING state.
keyready will move the session to the READY state. keyerror to the ERROR state.

At any time, for CDM specific reasons, it may be necessary to return from the
READY state to the PENDING state. This might occur for some form of key
rotation, for example.

We propose to add a state attribute to the session and a new keyready event.

It is an open question whether we should keep the keyadded event. It's not
clear what action someone might take from keyadded but it also doesn't seem
cause harm to include it.

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

Received on Tuesday, 18 June 2013 14:49:08 UTC