refactor: adjust inline comment for packet loss metric usage
Adjust an inline comment in connection status' service about packet loss metric usage. Now it correctly states that the absolute counter SHOULD NOT be used for alert triggers.
This commit is contained in:
parent
1eafe4b621
commit
3fbe4be441
@ -69,8 +69,8 @@ export const handleAudioStatsEvent = (event) => {
|
||||
//
|
||||
// This metric is DIFFERENT from the one used in the connection status modal
|
||||
// (see the network data object in this file). The network data one is an
|
||||
// absolute counter of INBOUND packets lost - and it should be used to determine
|
||||
// alert triggers
|
||||
// absolute counter of INBOUND packets lost - and it *SHOULD NOT* be used to
|
||||
// determine alert triggers
|
||||
connectionStatus.setPacketLossStatus(
|
||||
getStatus(window.meetingClientSettings.public.stats.loss, loss),
|
||||
);
|
||||
|
Loading…
Reference in New Issue
Block a user