Re: Another API issue: addStream has no callbacks

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.

/Adam

Received on Tuesday, 26 February 2013 07:18:14 UTC