- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2017 21:24:32 +0000
- To: public-webrtc-logs@w3.org
I think the reason is that in ORTC those candidates are emitted from a gatherer which doesn't have a component (i remember wondering about that...) @aboba do you mean there should be a way to determine which ice transport caused a candidate event to be fired? That would indeed be solved by adding a component (look up the transceiver based on mid, then use the candidate component to determine whether its the rtp or rtcp transport). The heavier alternative would be to add an ice transport to every ice candidate event... overkill? -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1167#issuecomment-299995302 using your GitHub account
Received on Monday, 8 May 2017 21:24:38 UTC