- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Jan 2017 19:46:21 +0000
- To: public-webrtc-logs@w3.org
The implementation I think makes the most sense is that one attaches to the destructor of each object a call that "pickles" the stats and stores it in a table for later stats calls to return. The alternative is that objects (that may consume resources or influence events) between two stats calls are permanently invisible to the stats API - this did not seem like a desirable feature. ie if you have stats at 5-second intervals, and someone is doing 1-second datachannels, you will never see anything about them (except the counters in the peerconnection stats object increasing). -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/114#issuecomment-271677904 using your GitHub account
Received on Tuesday, 10 January 2017 19:46:31 UTC