[Bug 26683] Replace MediaKeyMessageEvent's "destinationURL" attribute with a "type" attribute

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

Joe Steele <steele@adobe.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steele@adobe.com

--- Comment #1 from Joe Steele <steele@adobe.com> ---
This is much less onerous than removing the URL entirely. But I still have some
concerns. In the future we may wish to support "federated content" where a
single player can playback content from multiple content publishers. 

Today that can be done with some DRM schemes by providing that information in
the PSSH box. I can see a couple of ways of doing within this scheme but I am
not sure whether they will work for everyone.

1) The most obvious way is to include the URL inside the message being sent and
then have a single front-end key server decode the message and forward it to
the appropriate backend server. This removes the complexity from the client
entirely. Is this the scheme you are hoping for? 

2) Another way to do this was suggested by Mark on another thread/bug. In that
proposal the CDM would encode the information along with the regular key
request message in a way that the client application can pull out and consume.
This would allow the application to control this process and reduce the
server-side processing at the expense of some client side complexity. Some
content providers may go this route to avoid the cost of another server. 

Are there other ways I am not seeing that might be better?

If (1) is the way folks really think is best, I think an a section should be
added that specifically explains this philosophy to try to head off folks going
down path (2). Maybe title it "Network Communications Guidelines"?

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

Received on Tuesday, 2 September 2014 17:13:02 UTC