W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2015

Re: Question: how should addTrack work in relation to createOffer et. al.?

From: Jan-Ivar Bruaroey <jib@mozilla.com>
Date: Mon, 04 May 2015 11:23:31 -0400
Message-ID: <55478EF3.4000400@mozilla.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 5/4/15 2:39 AM, Stefan Håkansson LK wrote:
> On 03/05/15 22:55, Harald Alvestrand wrote:
>> On 05/03/2015 08:41 PM, Stefan Håkansson LK wrote:
>>> On 03/05/15 18:07, Harald Alvestrand wrote:
>>>> This means to me that Jan-Ivar's resolution can be correct unless we
>>>> change addTrack.
>> Ouch. I misread this part. We are changing the tracks structure outside
>> the operations queue by AddTrack.
>> I think that's a mistake, but I can't argue that it's not in the spec :-(

Care to argue for why you think it is a mistake, to allow for a 
discussion that leads to a joint understanding of the issue?

> Perhaps add/removeTrack should be part of the same queue.

Perhaps not.

> (I was thinking about a more radical proposal: remove the queue and
> force the application to wait for promises to resolve before moving on.

What problem do you attribute to the existence of the queue exactly?

> THis would be more in line with the vein of JSEP ("move the state
> handling to the app") IMO. But I think there are cases that makes this a
> bad idea.)

I think at this point we should demand reasons for why a change should 
be considered, before looking for reasons not to.

.: Jan-Ivar :.
Received on Monday, 4 May 2015 15:24:01 UTC

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