| commit | 059d0e364c166e0bd2cb93b25fddb096067cffa7 | [log] [tgz] |
|---|---|---|
| author | hbos <hbos@webrtc.org> | Tue Aug 30 21:04:35 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Tue Aug 30 21:04:40 2016 |
| tree | 45f1963171fc7f6e8bb7f8e98a0a03af938d9119 | |
| parent | 854d164fae9b0d4a2703d0bfb105bd4151b60ed3 [diff] |
RTCStatsCollector and RTCPeerConnectionStats added. This is the stats collector for the new stats types, RTCStats[1] and RTCStatsReport[2]. It so far only produces RTCPeerConnectionStats[3] as an example of how it would collect stats. Each RTCStats subclass will get a corresponding RTCStatsCollector::ProduceFooStats(). Stats reports are cached and returned as const references (ref counting). This allows stats to be inspected by multiple observers and across multiple threads. No copies will have to be made when surfacing this to Blink or other places. The current implementation of ProducePeerConnectionStats() only look at existing DataChannels. This might be incorret if data channels can be removed? Will investigate in a follow-up, crbug.com/636818. [1] https://www.w3.org/TR/2016/WD-webrtc-20160531/#idl-def-rtcstats [2] https://www.w3.org/TR/2016/WD-webrtc-20160531/#rtcstatsreport-object [3] https://w3c.github.io/webrtc-stats/archives/20160526/webrtc-stats.html#pcstats-dict* BUG=chromium:627816, chromium:636818 Review-Url: https://codereview.webrtc.org/2242043002 Cr-Original-Commit-Position: refs/heads/master@{#13979} Cr-Mirrored-From: https://chromium.googlesource.com/external/webrtc Cr-Mirrored-Commit: d565b73121b1b7672fb7d1f115bbbbb137a838eb