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

ReplaceTrack - need to evaluate alternatives

From: Harald Alvestrand <harald@alvestrand.no>
Date: Mon, 13 Apr 2015 10:51:50 +0200
Message-ID: <552B83A6.2040405@alvestrand.no>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
<chair hat>
At the October 2014 TPAC, we had a presentation on the proposed 
ReplaceTrack function.

Despite some misgivings (OK, a lot of them mine) about the way 
ReplaceTrack works with the identifiers of tracks, the WG decided to go 
ahead with adopting ReplaceTrack, and asked for a complete proposal.

At the moment, we have two proposals for ReplaceTrack or equivalent up 
as pull requests, both by Jan-Ivar.

The two proposals are:

https://github.com/w3c/webrtc-pc/pull/195 - 
RTCRTPSender.ReplaceTrack(MediaStreamTrack withTrack)

https://github.com/w3c/webrtc-pc/pull/196 - RTCRTPSender.track attribute

Both proposals suggest that the action of replacing a track either fires 
negotiationnneeded or "just switches". Neither proposal says what 
happens to the identifiers on the receiving side - presumably they would 
be unchanged in the "no signalling" case, but I'm not sure what would 
happen in the "signalling" case.

We have to decide:

a) whether the proposals are complete enough to evaluate or not

b) whether the proposals' suggestions for how to handle signalling is 
the right one

c) if we prefer the "replaceTrack()" or ".track" representation of the 
functionality.

Comments welcome!

           Harald
Received on Monday, 13 April 2015 08:52:20 UTC

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