- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Oct 2017 08:53:38 +0000
- To: public-webrtc-logs@w3.org
My thinking about the beginning vs end was with extensibility, but when I think about it again, I realize that I was thinking C++ enums that map to numbers; WebIDL enums map to strings, so order really doesn't matter. wrt partial enums, they don't seem to have made it into WebIDL so far. https://www.w3.org/Bugs/Public/show_bug.cgi?id=27048 is a bug filed in 2014 about it. wrt vpn: my thinking is that if we know something's going out over Ethernet, we should say so, even if it's vpn-encapsulated. But it makes sense to me to differentiate between "can't tell" and "can't tell because it's a VPN", so having a vpn member for the case where we can't tell what's the real interface makes sense. (My thinking of usage of this enum is that it will be used for collecting stats on "what's the typical distribution of bandwidths when people have an Ethernet interface vs a WiFi interface" - VPN is more useful than "unknown", but less useful than the physical-interface distinction.) -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/259#issuecomment-338921281 using your GitHub account
Received on Tuesday, 24 October 2017 08:53:40 UTC