[Bug 24016] Multiple outstanding key requests allowed

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

--- Comment #5 from Joe Steele <steele@adobe.com> ---
(In reply to Adrian Bateman [MSFT] from comment #4)
> (In reply to Joe Steele from comment #3)
> > This could also be handled in the app by tracking all the outstanding
> > requests and sending the responses down in serial order. I guess we could
> > write some boilerplate code for that and post it somewhere?
> 
> Can't the CDM cache or drop out of order responses? Presumably if this is
> common (because the requests are taking too long) then sooner or later
> playback is going to fail because the license service isn't keeping up with
> the media?

It may be impossible for the CDM to distinguish between a response received out
of order and a corrupted response, if the responses are encrypted. 

If the server lag is long-term, playback *is* going to start failing and it
probably doesn't matter if the CDM fails because of out of order responses or
because it can't get the keys fast enough. If the server lag is momentary,
playback could start failing but might be able to continue if it receives
responses in the right order. 

I think we can probably wait to see whether this is a problem in the real
world. After some research into real-world heartbeat usage I don't think this
scenario is common enough to worry about at this point. I will go ahead and
close this.

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

Received on Friday, 6 December 2013 18:29:14 UTC