Re: [webrtc-pc] replaceTrack and removeTrack: Synchronous?

FWIW, it seems to me that `replaceTrack` does quite a bit of things (I mean that the content of the RTP packets going over the wire change), while `addTrack` does almost nothing (it mostly returns a sender, but that sender's transports are `null`). To get anything out of an `addTrack` you need to do the createOffer, setLocal..... things.

As @jan-ivar points out in there can be cases when an off-main-thread examination of the source would be needed for `replaceTrack`. 

Are there strong reasons why we would change `replaceTrack`?

GitHub Notification of comment by stefhak
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 2 January 2018 09:59:41 UTC