W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2017

Re: [webrtc-pc] Missing definition for obtaining list of all RTCIceTransport and RTCDtlsTransport

From: Soares Chen via GitHub <sysbot+gh@w3.org>
Date: Fri, 02 Jun 2017 06:54:09 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-305705426-1496386447-sysbot+gh@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.

Got it then. Having something like an `ontransport` event on the sender/receiver could simplify a lot on the transport management.

I agree that having public getIceTransports() and getDtlsTransports() methods might not help much in most other cases. Although would it be helpful to have private sections in the spec to describe the steps to get all Ice and DTLS transports? That could be refactored/modified out from the `close()` method and be shared with other sections such as the connection state change event sections.

-- 
GitHub Notification of comment by soareschen
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1306#issuecomment-305705426 using your GitHub account
Received on Friday, 2 June 2017 06:54:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:43 UTC