- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Sep 2022 17:22:54 +0000
- To: public-webrtc-logs@w3.org
Agreed with the inherent raciness here given channel might run in a worker and negotiation happens in window. I see a few possibilities: - Remove the synchronous maxMessageSize check and silently fail. - Remove the synchronous maxMessageSize check and provide failure notification in some async manner. - Add a maxMessageSize slot in the data channel and use it for the synchronous check. Consider maxMessageSize is frozen at transfer time. - Same as above but update maxMessageSize by posting a task to the transferred data channel. During the window where the value is not updated, silently fail. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/114#issuecomment-1252671383 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 September 2022 17:22:56 UTC