- From: <bugzilla@jessica.w3.org>
- Date: Sat, 26 Oct 2013 04:57:38 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21798
David Dorwin <ddorwin@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adrianba@microsoft.com
--- Comment #13 from David Dorwin <ddorwin@google.com> ---
Should the ERROR state be terminal? In the current state machine, it appears to
be so.
Some scenarios to consider:
* Output protection error: the session might have other keys whose requirements
can be met when new media data is provided. Should we really require that a new
session be created (along with the accompanying message exchange and associated
latency)?
* License renewal: If a license expires because it cannot be renewed (i.e. lost
network connection) then can subsequently be renewed, should we require that
the application start over with a new license request when it could just
provide a renewal message (via update())?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 26 October 2013 04:57:39 UTC