Re: replaceTrack proposal

On 3 September 2014 11:31, Peter Thatcher <> wrote:
> If the sender changes to a different local source of media, what does
> the receiver need to know about it?  Could we simply changing nothing
> (no renegotiation or change of identifiers), and just treat it at as
> purely sender-side change?    I suppose that may mean what appears as
> Track A to the receiver actually comes from Track B on the sender.  Is
> this a serious problem?  Are there other problems that you see?  It
> doesn't seem like a big deal to me.

I was always of the opinion that copying the stream and track
identifiers through was a bad idea.  We probably needed to add a new
sort of identifier for correlation purposes rather than try to
superimpose two namespaces like we have.

So this works perfectly well, if you are OK with essentially removing
the identifier requirements we have already agreed to.

Received on Wednesday, 3 September 2014 18:35:20 UTC