- From: Lenny via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Sep 2022 07:08:56 +0000
- To: public-webrtc-logs@w3.org
> I don't see why we need both. If we freeze it then there's no race, and apps can forward the info at its leisure. If we give RTCDataChannels an internal slot, then we can update this info across threads, and don't need to freeze them. Arguably, there could still be a race between O/A updating `maxMessageSize` and the data channels accessing their slot. But, as explained, I think it's completely irrelevant. There is no use case to update the value, so I'd suggest to go with what's simplest to implement. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/114#issuecomment-1259077540 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 September 2022 07:08:58 UTC