- From: Lenny via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Nov 2021 08:42:17 +0000
- To: public-webrtc-logs@w3.org
Expanding on what I mean with guard checks then: If the port restriction applies to all connections for the whole port range, then there should be no problem on spec level. Of course, that's different in practical implementations since there isn't just _the one way_ to create sockets and initiate connections. For example, last time I checked Firefox used an ICE library underneath. Hacking this into the library could not only be painful but it's also easy to miss something. It's likely easier to fence off PC methods entirely and simulate a network failure - that means guard checks. And at that point, we need to ask if it's worth the effort. But beyond that, as a developer I would also rather like to have explicit signals that WebRTC is turned off. Finding it out by listening for an ICE failure (which can take many seconds as @jan-ivar mentioned) isn't great. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/81#issuecomment-978957574 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 November 2021 08:42:19 UTC