- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Sep 2022 21:36:39 +0000
- To: public-webrtc-logs@w3.org
> 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, ... Lost or transferred...? Is being able to close transferred data channels from main thread part of the stated goal here? > As long as we are ok removing the transferred data channel from the list returned by getDataChannels(), we should be good. What's the point of enumerating datachannels if it excludes some active data channels? > 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. Note this is https://github.com/w3c/webrtc-pc/issues/2624 and does not require a new API by itself. Presumably, we want the pc to hold transferred data channels alive too? Thus, an internal slot might want to keep them on the list? > Edit 2: I'm not sure invalidation is the correct term but I hope you get what I mean. The original becomes _"detached"_. See https://github.com/w3c/webrtc-extensions/issues/115. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/110#issuecomment-1258661131 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 September 2022 21:36:41 UTC