W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2018

Re: [webrtc-pc] Semi-sync replaceTrack API pre-initial-negotiation is bizarre.

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Mon, 12 Feb 2018 22:27:17 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-365084519-1518474436-sysbot+gh@w3.org>
so (reconstructing argument from memory) the sequence

tc = pc.addTransceiver()

should have the track as part of the offer; anything else surprises the user.
in order to guarantee that, the setting of the track has to happen in the synchronous section.

thus, this is required in order to be able to construct pc.addTrack() on top of addTransceiver() and replaceTrack().
Seems hard to get away from that.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1769#issuecomment-365084519 using your GitHub account
Received on Monday, 12 February 2018 22:27:20 UTC

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