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

Re: ReplaceTrack and track.id (Re: ReplaceTrack - need to evaluate alternatives)

From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 15 Apr 2015 17:12:45 -0700
Message-ID: <CAJrXDUGfQz+DqopF_SvaiPhFass-WfpOxP-EU5VGpp5msP-MVw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Ah, I see.  It's true that if we didn't allow JS to choose the value, it
would be the same as now where the JS cannot choose the track ID.  So we
wouldn't be losing anything compared to the status quo.

But isn't the JS always able to set it anyway via SDP munging?

On Wed, Apr 15, 2015 at 3:24 PM, Martin Thomson <martin.thomson@gmail.com>

> On 15 April 2015 at 15:19, Peter Thatcher <pthatcher@google.com> wrote:
> > And te question isn't whether to allow the JS to choose the MID.  It's
> > whether to have two IDs/labels (MID + something else), or just one (MID).
> > If one will work, I prefer one.
> Like I said, I am OK with just one and with that one being a=mid; I
> was pushing back at your suggestion that we let the JS set it, that's
> all.
Received on Thursday, 16 April 2015 00:13:56 UTC

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