Agreed @alvestrand. However, regarding the **current** API addition proposal, my opinion is that it's not needed and that the requested API is incomplete (in the sense that not just `RTCPeerConnection.id` would be needed, but also a global `getRTCPeerConnectionById()` method). Now, let's go to ORTC spec in which there is no `RTCPeerConnection`. Following the rationale of this API proposal, we'd also need more and more methods such as `getRTCIceTransportById()`, `getRTCDtlsTransportById()`, `getRTCRtpSenderById()`, etc. Even more, we would also need `WebSocket.id` plus `getWebSocketById()`, and `AudioContext.id` plus `getAudioContextById()` and so on. -- GitHub Notification of comment by ibc Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-366960642 using your GitHub accountReceived on Tuesday, 20 February 2018 12:21:35 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:43 UTC