- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Mar 2017 19:20:30 +0000
- To: public-webrtc-logs@w3.org
taylor-b has just created a new issue for https://github.com/w3c/webrtc-pc: == Range checking needed for iceCandidatePoolSize == For one, `iceCandidatePoolSize` should probably be using `[EnforceRange]`, so that (for example) a value of -1 isn't converted to 65535 at the WebIDL level. We also might want to restrict the 0-65535 range further. There shouldn't be any scenario where more than a handful of pooled candidates will be needed, and allowing WebRTC to take up every single available socket is probably not desirable. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1048 using your GitHub account
Received on Thursday, 2 March 2017 19:20:36 UTC