W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 21855] Avoid network traffic and duplicate sessions for the same key(s)

From: <bugzilla@jessica.w3.org>
Date: Tue, 15 Oct 2013 04:48:46 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-21855-2486-2suzBvlxr6@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21855

--- Comment #8 from David Dorwin <ddorwin@google.com> ---
(In reply to Adrian Bateman [MSFT] from comment in bug 17750)
> ... there is no explicit sharing - just
> that you don't necessarily need to go through PENDING to get to READY.

So sharing (or any other method to bypass PENDING) is an implementation detail,
but the CDM must do whatever is necessary to present the sessions as
independent? That includes firing events at each session to transition states,
handling close() (bug 17750) on each session without clearing keys in use by
other sessions(?), etc.

(In reply to Adrian Bateman [MSFT] from comment #7)
> ... If a
> session needs to go back to PENDING it does so independently (meaning all
> "shared" sessions may also go back to PENDING).
> 
> This avoids the questions about which sessions should receive subsequent
> messages...

Does this mean the CDM must either a) fire the keymessage at each "shared"
session and thus transition them to PENDING or b) fire the keymessage at one
session and leave the others in CREATED/READY until they are READY or an error
occurs?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 15 October 2013 04:48:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:44 UTC