[Bug 16553] Consider not firing a needkey event when a potentially encrypted stream is encountered if the key is already known

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

--- Comment #4 from David Dorwin <ddorwin@google.com> 2012-09-05 13:51:31 UTC ---
(In reply to comment #3)
> The way I read step#5 of the createSession() method, a keymessage event will
> always be fired. This is going to be unnecessary overhead in cases where the
> key is already known, either because it was previously acquired and is still
> live or because it was embedded in the initData. Can we simply not fire that
> message if the key is already available?

This is related to the algorithm in 5.2, which results in a "needkey" event.
The "keymessage" event you refer to is not directly related. Since
createSession() is always called by the application, the application is causing
the keymessage events, which it needs in order to request a license. The
application can avoid calling createSession() in response to a needkey event
regardless of the outcome of this bug.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 5 September 2012 13:51:37 UTC