W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2013

Re: Another API issue: addStream has no callbacks

From: Justin Uberti <juberti@google.com>
Date: Tue, 26 Feb 2013 07:24:04 -0800
Message-ID: <CAOJ7v-3f3oSMoKxWii8dmKZSJrWBf0ryJvrxo4E6EUZrAK4tDA@mail.gmail.com>
To: Adam Bergkvist <adam.bergkvist@ericsson.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Mon, Feb 25, 2013 at 11:17 PM, Adam Bergkvist <
adam.bergkvist@ericsson.com> wrote:

> On 2013-02-26 03:13, Justin Uberti wrote:
>> There may be reasons for addStream to fail (e.g the PeerConnection has
>> been closed), but I don't think exhausting encoders is one of them. Any
>> resources are not reserved until createOffer/setLocal.
>> addStream simply adds the supplied stream to the list of local streams
>> known to the PeerConnection.
> and fires the negotiationneeded event when appropriate.
> As far as I see it (which may not be the entire picture), the failures we
> need to deal with here belongs to the category of bad input and state. And
> those can be dealt with using exceptions.

That matches my understanding.
Received on Tuesday, 26 February 2013 15:24:52 UTC

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