- From: Florent Castelli via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Jul 2022 09:34:23 +0000
- To: public-webrtc-logs@w3.org
> For logical consistency, I think it's the SctpTransport that should have a strong reference to the data channels it carries, not the RTCPeerConnection. But the RTCPeerConnection should have a strong reference to the SctpTransport (assumption to be verified!), so the result is equivalent. The problem there is that you don't have a `RTCSctpTransport` object before negotiation if I read the spec correctly. But you can create as many data channel objects before negotiation as you want. Because of this reason, the data channels should be owned by the `RTCPeerConnection` object. I would advocate the data channels could have a reference to their `RTCSctpTransport` object, it'd make it easier for them to check the `max-message-size` during a `send()`. -- GitHub Notification of comment by Orphis Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2624#issuecomment-1174842789 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 July 2022 09:34:25 UTC