- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Mar 2019 15:58:18 +0000
- To: public-webrtc-logs@w3.org
> (Another difference is that removeTrack is synchronous, while replaceTrack has two levels of "queue a task". Do we care?) I guess this optimization is possible because removeTrack() does not need to acquire new encoding resources. replaceTrack(null) could probably special-case to be synchronous, but it already returns a promise, so I think it would just be confusing. "Do we care?" Meh. But considering this is all shipped, we shouldn't change the async/sync behaviors. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2024#issuecomment-472061353 using your GitHub account
Received on Tuesday, 12 March 2019 15:58:20 UTC