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: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Mon, 12 Feb 2018 21:38:43 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-365070941-1518471522-sysbot+gh@w3.org>
> But this leaves users with a bizarre API: if an error happens, they won't know which one until later. So it's never a fully synchronous API even in the pre-negotiation phase.

But the only errors possible at this point are calling `replaceTrack` while the transceiver is stopped, or calling `replaceTrack(audioTrack)` on a video sender, which are both user error. So is this really a problem?

GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1769#issuecomment-365070941 using your GitHub account
Received on Monday, 12 February 2018 21:38:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:00 UTC