- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Jun 2019 07:38:47 +0000
- To: public-webrtc-logs@w3.org
while that is mostly guaranteed by timing (gathering candidates takes time), iceCandidatePoolSize is interesting. The intent in [JSEP is pretty clear](http://rtcweb-wg.github.io/jsep/#rfc.section.3.5.4), gather but surface only via onicecandidate which avoids duplicate candidates and the need to filter them as mentioned [here](https://github.com/feross/simple-peer/issues/469) -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2199#issuecomment-498147178 using your GitHub account
Received on Monday, 3 June 2019 07:38:51 UTC