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

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

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 23 Apr 2015 12:34:33 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1D1F3D04@ESESSMB209.ericsson.se>
The current spec is pretty clear on how addTrack works in isolation:

a RTPSender is synchronously returned.

However, how addTrack relates to related (enqueued) operations is less 

As an example, for the sequence

var senderX = pc.addTrack(trackX);
var senderY = pc.addTrack(trackY);

1. would track/senderY be represented in the offer in any case?
2. if so, would it be consistently represented in the offer or would it 
depend on e.g. queue status?

One way to spec this would be to say that createOffer takes a snapshot 
of the current senders when called, and changes between that snapshot 
and the actual execution of createOffer are not taken into account. Is 
this the way we should go?

(This relates to github Issue #156 for webrtc)

Received on Thursday, 23 April 2015 12:34:59 UTC

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