W3C home > Mailing lists > Public > public-html@w3.org > April 2012

[Bug 16614] New: There is no way to correlate multiple generateKeyRequest calls with their responses

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Apr 2012 16:18:30 +0000
To: public-html@w3.org
Message-ID: <bug-16614-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16614

           Summary: There is no way to correlate multiple
                    generateKeyRequest calls with their responses
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Encrypted Media Extensions
        AssignedTo: adrianba@microsoft.com
        ReportedBy: watsonm@netflix.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


The current API design allows for multiple parallel key requests to be in
flight. Each call to generateKeyRequest() begins a message exchange resulting
ultimately in a keyadded or keyerror event. The first keymessage event may
contain a Session ID identifying the session. This session ID is later used to
enable correlation between messages conveyed in keymessage and responses added
in addKey.

However, the current design does not support correlation between specific
generateKeyRequest() calls (and the needkey event that might have triggered it)
and subsequent sessions. If a page knows it needs two keys, it can call
generateKeyRequest() twice but there is no way to know which keymessage or
keyerror results from each call. This might be particularly important for the
error case. Modifications to the API such as those described in Object-Oriented
API Design (https://www.w3.org/Bugs/Public/show_bug.cgi?id=16613) could address
this issue.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 4 April 2012 04:12:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:47 GMT