W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2017

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

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Tue, 10 Jan 2017 19:35:13 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-271674806-1484076912-sysbot+gh@w3.org>
@nils-ohlmeier Filtering in JS is so trivial, that for something to 
qualify as a selector, I think there also has to be a performance 
benefit (i.e. the implementation can skip a lot of gathering). Since 
there's (in theory!) no cap on the number of tracks that can be added 
to a peer connection, selecting on track makes sense based on that 
measure IMHO.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at 
https://github.com/w3c/webrtc-stats/issues/116#issuecomment-271674806 
using your GitHub account
Received on Tuesday, 10 January 2017 19:35:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:41 UTC