Re: [webrtc-stats] RTCPeerConnection.getStats: What to do with 'selector' argument?

"Maybe a sensible alternative would be to add more/different filters 
to the getStats() call, to allow filtering down into the transport 
specifics stats only." reminds me of what @alvestrand [just 
> History: We added selectors to the spec because we thought they'd be
 useful, and added tracks as a selector because that was the only 
clear case we could think of at that moment. The discussion tended to 
say "this will become an union, but since we only have one case now, 
we'll specify that case".

On the other hand, if you're looking for specific stats it's easy to 
filter them yourself. Using selectors for filtering makes more sense 
to me if they pick out only a small subset of the overall stats, just 
the thing(s) you're asking for (i.e. probably not a bunch of transport
 stats when asking for tracks), and hopefully at a lower cost than a 
full getStats() call.

GitHub Notification of comment by henbos
Please view or discuss this issue at 
using your GitHub account

Received on Tuesday, 10 January 2017 09:44:13 UTC