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

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

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Fri, 8 May 2015 13:43:36 +0000
To: Jan-Ivar Bruaroey <jib@mozilla.com>, Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1D1FD91A@ESESSMB209.ericsson.se>
Trying to summarize this discussion:

It seems that there is agreement:

* the offer created by createOffer will only take into account the 
senders (and their respective settings) that exist at the time when 
createOffer is called - anything that happens after will not be reflected

Is this right?

Second, what does that mean related to PR #222?

https://github.com/w3c/webrtc-pc/pull/222

Stefan


On 06/05/15 14:21, Jan-Ivar Bruaroey wrote:
> On 5/5/15 1:31 PM, Harald Alvestrand wrote:
>> On 05/04/2015 10:29 PM, Jan-Ivar Bruaroey wrote:
>>> You're right! Though, as I understand it, this is a matter of good
>>> spec design rather than some implicit guarantee or assumption (e.g.
>>> why we have "queue a task" everywhere).
>>
>> I think it is actually a hard requirement.
>
> No question. I merely meant it needs to be explicitly addressed in the
> spec as opposed to implicitly assumed.
>
>> Otherwise, stuff as simple as
>>
>>    a = new ObjectWithHandlerForAsynchronousEvent():
>>    a.handler = function() {}
>>
>> would never function reliably.
>
> Agreed.
>
>> People used to other languages who come to Javascript always recoil in
>> horror and ask "but where's the critical section?" when they see code
>> like this.
>
> Yes, that's a learning curve for sure, but getting those  critical
> sections out of people's hands is a good thing.
>
> .: Jan-Ivar :.
>
Received on Friday, 8 May 2015 13:44:03 UTC

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