[Bug 24016] Multiple outstanding key requests allowed

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

--- Comment #3 from Joe Steele <steele@adobe.com> ---
(In reply to David Dorwin from comment #1)
> What specifically is the problem with such outstanding requests that you're
> trying to address? In other words, why do the requests and responses need to
> be associated (other than perhaps within the server-CDM protocol)?

The requests may need to be processed in serial order. For example if request
N+1 relies on information provided in response N. If the responses arrive in
the wrong order, the processing could fail, even though the correct responses
are all available. 

(In reply to Adrian Bateman from comment #2)
> Presumably any value that could be passed into the update() call as an 
> additional parameter could also be included in the response from the server
> for those CDMs that need this?

True - however that would not allow supporting existing servers and content
tied to those servers. 

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?

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

Received on Friday, 6 December 2013 17:53:53 UTC