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

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

--- Comment #9 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
(In reply to David Dorwin from comment #8)
What I meant was to propose that there is no such thing as a "shared" key,
except perhaps during the acquisition as an optimization (skipping PENDING). I
don't think there is anything to prevent implementations being smarter if they
want but note that firing keymessage at multiple sessions _will_ result in
multiple connections to the license service. I don't think the spec should do
anything explicitly to describe how to manage this.

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

Received on Tuesday, 15 October 2013 14:23:22 UTC