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: Mon, 30 Mar 2020 09:11:54 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-605879424-1585559513-sysbot+gh@w3.org>
My position:
- I am against Behavior A because it blocks the JS thread on "in-parallel" work, effectively making them not "in-parallel". Chrome's WebRTC implementation is violating Chromium design principles.
- I am against Behavior B because it is racy.
- I believe Behavior C is the "correct behavior" but I'm afraid fixing the implementations are not worth the benefits. Is there a compromise?

I am happy with updating the spec such that minimum work is required on behalf of browser vendors (ideally none). But right now, I feel like the correct behavior is either undefined or not what current implementations are doing today.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2502#issuecomment-605879424 using your GitHub account
Received on Monday, 30 March 2020 09:11:57 UTC

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