- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Sun, 11 Jun 2017 22:34:23 +0000
- To: public-webrtc-logs@w3.org
I am not exactly sure what 'performance degradation' means. In some cases, encoding/decoding may totally stop. In that case, getStats could be used to detect when encoding/decoding is failing. But it seems weird to do continuous calls to getStats just for that reason. It also does not give any hint to the web application of the actual error and might not be very responsive. If an error event was sent (or something equivalent like an error callback) with some reason of the error, it would be much simpler/quicker/easier for the web application to react upon it. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1323#issuecomment-307661490 using your GitHub account
Received on Sunday, 11 June 2017 22:34:29 UTC