[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 #10 from David Dorwin <ddorwin@google.com> ---
I am also in favor of removing the existing text and always firing a needkey,
relying on the application to handle duplicate Initialization Data.

One of the most important reasons is that there is no guarantee that the user
agent can determine whether all the keys associated with the Initialization
Data have already been received. For example, there is no guarantee that the
CENC PSSH lists all key IDs it represents.

One thing the user agent could do is avoid sending duplicate needkey events for
the same Initialization Data. For example, if the PSSH is exactly the same for
audio and video or for two video streams in adaptive streaming. A single bit
difference, would nullify this, though, so it might be best to leave to the
application/server.


I think the main question is how much burden is it on an application to compare
(and possibly track) Initialization Data to avoid calling createSession()
multiple times for the same data? Also, is the common logic that each
application might need to include worth complicating the user agents and
possibly restricting use cases?

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

Received on Sunday, 10 March 2013 05:28:24 UTC