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

[Bug 16550] New: Should sessionId checks in addKey() and cancelKeyRequest() be synchronous?

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Mar 2012 00:22:57 +0000
To: public-html@w3.org
Message-ID: <bug-16550-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16550

           Summary: Should sessionId checks in addKey() and
                    cancelKeyRequest() be synchronous?
           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: ddorwin@google.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


>From v0.1:
Should this be handled {in the synchronous portion of the addKey() algorithm}
or in the task scheduled in the next step. The advantage of handling it here is
that what is likely a programming error is immediately and simply reported via
an exception. The disadvantage is that the user agent must store session IDs
(and track when they are released) for each Key System rather than letting the
CDM manage them. This is inconsistent with the goal that the user agent should
just pass information. This same issue also applies to cancelKeyRequest().

-- 
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, 28 March 2012 02:17:31 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:31 UTC