- From: Florent Castelli via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jun 2022 16:08:56 +0000
- To: public-webrtc-logs@w3.org
Orphis has just created a new issue for https://github.com/w3c/webrtc-extensions: == Add getDataChannels() method on RTCPeerConnection == Similar to the `getTransceivers()`, `getSenders()` and `getReceivers()`, I believe we would benefit from having a `getDataChannels()` method to list all the data channels that have been created and are not in `closed` state. Currently, if the handle to a data channel is "lost", it's not possible to close it until the peer connection it belongs to is closed, or possibly if the implementation decides to close a garbage collected data channel (but since we haven't defined object lifetimes, it may not happen). Having the peer connection owning a reference to the data channels would allow to properly extend the data channel lifetime to match the peer connection's lifetime too at least. It would also be quite valuable to have for testing and any sort of introspection. Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/110 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 June 2022 16:08:58 UTC