W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2020

Re: [webrtc-pc] Restart process to apply description if addTrack called (#2504)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Tue, 31 Mar 2020 20:36:24 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-606860571-1585686982-sysbot+gh@w3.org>
> So if you do setRemoteDescription() followed by addTrack() the resulting behavior observed would always be as if you invoked addTrack() first and setRemoteDescription() second?


> Can you clarify, would this be any different from if you had awaited setRemoteDescription() first and performed addTrack() second?

I think the net result is the same, but I'd appreciate a second pair of eyes. The assumption here is that the incoming SRD creates a transceiver that we want to associate with. In the latter case, we'd be in `"have-remote-offer"` so this transceiver's currentDirection would still be `null` and satisfy the absorption criteria in [addTrack](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtrack). 

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2504#issuecomment-606860571 using your GitHub account
Received on Tuesday, 31 March 2020 20:36:26 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:50 UTC