- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Jun 2018 07:57:33 +0000
- To: public-webrtc-logs@w3.org
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc: == RTCIceTransport.component is at the wrong abstraction layer == The "component" of an RTCIceTransport returns either "rtp" or "rtcp", depending on what the ICE transport is used for. This is a layering mistake; if RTCIceTransport is to be a reusable component of other structures (like QUIC or data-channel-only sessions), this needs to be on the containing object, not on the contained object. The "component" is also present on the RTCIceCandidate, but there it serves to route a candidate to the correct transport when presented to the peerconnection; the peerconnection already knows which transport is the RTP and which is the RTCP if both are used. I suggest deleting this component from the interface. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1916 using your GitHub account
Received on Monday, 25 June 2018 07:57:35 UTC