Re: [webrtc-extensions] support disable ipv6 candidate in RTCConfiguration (#138)

It should be possible to filter out the candidates from the SDP as well.

Regarding collection time of candidates, I think this is fast in the lower layer, but if there are a lot of candidates (i.e. BUNDLE is not used and there are a lot of m= sections) then there can be an artificial delay added by the fact that each candidate gets surfaced in a separate task execution cycle and each candidate fires an event for each m= section. So if there are 100 candidates that should be exposed to JS that delays both candidates and the resolution of the SLD/SRD promise by 100+ task execution cycles, something which adds noticeable delays (we could talk seconds) of "processing time". This is an optimization bug though that could be solved by the browser implementation.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/138#issuecomment-1377142265 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 10 January 2023 11:50:36 UTC