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

Re: [webrtc-pc] The threading model of webrtc-pc: When are effects of in-parallel stuff surfaced? (#2502)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Tue, 31 Mar 2020 21:18:17 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-606881227-1585689496-sysbot+gh@w3.org>
I think the former and #2504 makes sense, but Chrome currently does the latter.
Assuming Chrome gets updated to [not expose the mid value prematurely](https://github.com/w3c/webrtc-pc/pull/2504#issuecomment-606874108), can you foresee any observable difference between doing the former or doing the latter?

If the end-result is the same, that we have an associated transceiver, then Chrome doing things sub-optimally would be a performance issue, not a spec-compliance issue. I'm hoping that to be the case.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2502#issuecomment-606881227 using your GitHub account
Received on Tuesday, 31 March 2020 21:18:21 UTC

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