- From: docfaraday via GitHub <noreply@w3.org>
- Date: Thu, 26 Feb 2026 15:10:56 +0000
- To: public-webrtc-logs@w3.org
While I realize that observability of GC is generally considered undesireable, webrtc lays claim to very observable, non-fungible resources. Ports, hardware encoders/decoders, TURN allocations (the TURN server is watching what you do!), and so forth. There is no escaping this. And, since we're in network protocol land, we have to remember that a transport association requires two to tango; either side can unilaterally decide it is done. The transport code in browsers see this all the time and cope with it just fine by surfacing events, this is just a super-rare case where the other side *might* happen to be another browser. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3090#issuecomment-3967245619 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 February 2026 15:10:57 UTC