- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Jun 2017 05:10:48 +0000
- To: public-webrtc-logs@w3.org
As Taylor noted, there is an existing issue relating to when the Ice and DTLS transports are created, which when fixed will tell us when receiver/sender.transport and receiver.sender.transport.transport will be non-null, which makes enumeration considerably simpler. Even if we had native getIceTransports() and getDtlsTransports() methods (or developed them based on the existing APIs), calling these methods before Ice or DTLS transports are created would not provide all the transports. So you'd need to figure out which RtpSenders/Receivers had transports and which didn't to determine which transports were missing - the same problem you noted without those methods. Even if they did return all the Ice or DTLS transports, if you needed to know which RtpSenders/RtpReceivers they corresponded to, then you'd still need to enumerate all the senders and receivers. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1306#issuecomment-305691138 using your GitHub account
Received on Friday, 2 June 2017 05:10:54 UTC