W3C home > Mailing lists > Public > public-webrtc@w3.org > September 2011

Re: Error handling

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 6 Sep 2011 19:56:00 +0000 (UTC)
To: Tommy Widenflycht (ᛏᚮᛘᛘᚤ) <tommyw@google.com>
cc: Justin Uberti <juberti@google.com>, public-webrtc@w3.org
Message-ID: <Pine.LNX.4.64.1109061953450.9867@ps20323.dreamhostps.com>
On Mon, 5 Sep 2011, Tommy Widenflycht (~[~O~Z~[~X~[~X~Z) wrote:
>
> TYPE_ERROR is common as well and is probably the correct action for the 
> three first cases.

Some of these are already handled:

> On Sat, Sep 3, 2011 at 00:15, Justin Uberti <juberti@google.com> wrote:
> 
> > The current specification indicates that INVALID_STATE_ERR exceptions may
> > be thrown if methods are called on a PeerConnection that is in the wrong
> > state. However, other sorts of errors can of course occur:
> > - a bad object (i.e. not a MediaStream) is passed to addStream

That's handled by WebIDL.


> > - processSignalingMessage receives an malformed signaling blob
> > - processSignalingMessage receives an incompatible description (no codecs,
> > incompatible codecs, incompatible crypto)

That's handled by the ICE and SDP specs, in theory. The API doesn't throw 
an exception because the processing has to be async.


> > - an internal failure occurs while processing an arbitrary API call

Internal failures are bugs, we can't very well specify what should happen 
in the case of bugs. :-)


> > - connectivity fails to establish, or is lost mid-call

That would cause the ICE Agent to attempt to reestablish the connection.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 6 September 2011 19:59:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:25 UTC