- From: <bugzilla@jessica.w3.org>
- Date: Fri, 06 Dec 2013 01:32:24 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24016 Bug ID: 24016 Summary: Multiple outstanding key requests allowed Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Encrypted Media Extensions Assignee: adrianba@microsoft.com Reporter: steele@adobe.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org It is possible for the browser get into a situation where multiple EME key requests are outstanding at the same time. Since they are asynchronous, the order the responses are received in is indeterminate. However there is no way to directly associate a response with its request today. Example: An application is playing back a video stream which makes frequent key requests (e.g. heart beat testing). If the delay between sending the request and receiving the response is longer than the heart beat interval, you are now in this situation. This could be addressed in a variety of ways: * We could explicitly say that no additional key requests may be sent for a given key session until the outstanding request has been completed. * We could require a URL to be passed in with the update() call which the CDM could match against the outstanding requests. * others? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 6 December 2013 01:32:26 UTC