ISSUE-3: Should we refactor the generic guidance on error handling out of the spec

Should we refactor the generic guidance on error handling out of the spec

State:
RAISED
Product:
Raised by:
Eric Rescorla
Opened on:
2013-11-12
Description:
The spec is full of "If connection's RTCPeerConnection signalingState is closed, throw an InvalidStateError exception and abort these steps."

I propose to pull this out and make it apply everywhere to the spec and then list the explicit exceptions.
Related Actions Items:
No related actions
Related emails:
  1. Re: ISSUE-3: Should we refactor the generic guidance on error handling out of the spec (from ekr@rtfm.com on 2013-11-14)
  2. Re: ISSUE-3: Should we refactor the generic guidance on error handling out of the spec (from martin.thomson@gmail.com on 2013-11-14)
  3. Re: ISSUE-3: Should we refactor the generic guidance on error handling out of the spec (from harald@alvestrand.no on 2013-11-14)
  4. ISSUE-3: Should we refactor the generic guidance on error handling out of the spec (from sysbot+tracker@w3.org on 2013-11-12)

Related notes:

No additional notes.

Display change log ATOM feed


Harald Alvestrand <hta@google.com>, Bernard Aboba <bernarda@microsoft.com>, Jan-Ivar Bruaroey <jib@mozilla.com>, Chairs, Dominique Hazaƫl-Massieux <dom@w3.org>, Carine Bournez <carine@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $