[Bug 26401] Key message destinationURL usage is not reflected in examples

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

--- Comment #5 from David Dorwin <ddorwin@google.com> ---
(In reply to Joe Steele from comment #4)
> (In reply to David Dorwin from comment #3)
> > Example 8.2 expects a single message per session^. As I noted in comment #1,
> > this is case #1 and the message is generated by createSession(). Thus,
> > event.destinationURL is NULL.
> 
> Ah -- I misread what you were saying. In that case I am objecting to that
> section of the createSession() algorithm (7.8). *Any* request sent by the
> CDM must have the opportunity to supply the URL to be used. 

Where would the URL come from?
> 
> > 
> > ^ This example is not robust and would likely fail in some real world
> > scenarios. We could consider making the examples more robust, but the goal
> > is to explain usage of the APIs without being overly complex. Maybe a simple
> > comment that a real application should handle multiple messages would be
> > sufficient.
> 
> This example will fail in general for any CDM which requires a per-origin
> initialization involving server communication.

Can you give an example where such initialization would fail? Why wouldn't the
server specified by licenseUrl for the key system be able to handle the
initialization? What server would be specified in destinationURL?

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

Received on Monday, 18 August 2014 22:16:50 UTC