Re: asynchrony for addStream w/ error/success callbacks

On Fri, Jan 10, 2014 at 9:04 AM, Jan-Ivar Bruaroey <> wrote:
> Good point about it being odd, tough I disagree it would be unrecoverable,
> as addStream would presumably push streams to a temporary list that
> createOffer discards (or prunes) if it fails.

And how am I to discover what went wrong? What a baffling API semantic.

> Should addStream(a), addStream(b), removeStream(a), createOffer() work? That
> would not be possible unless the validation was deferred (along with the
> rest of the actions) to createOffer.

Huh? The right thing here is simply to have AddStream() fail, which doesn't
leave you in this state at all.


Received on Friday, 10 January 2014 17:10:15 UTC