- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Jan 2018 15:39:14 +0000
- To: public-webrtc-logs@w3.org
Isn't this a typical problem that can be resolved with log rotation / a circular buffer? One could imagine an API to set the target size of the log buffer (where of course the browser still has the right to restrict the bounds) with a sane default. The only issues I see is a) how to determine the size of the current log entries, and b) how to make sure the application doesn't poll too slow if it wants to gather all information (maybe raise an event as proposed by @alvestrand). -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/235#issuecomment-356965101 using your GitHub account
Received on Thursday, 11 January 2018 15:39:33 UTC