- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Sat, 18 Jun 2022 09:55:26 +0000
- To: public-webrtc-logs@w3.org
Thanks for filing this issue, the lifetime issue deserves more attention. See https://github.com/w3c/webrtc-stats/pull/628#issuecomment-1159405398 regarding what happened and me filing an issue to make sure sender/receiver/transceiver gets its spot in the provisional spec. Where we are now: After a) the obsoletion of track stats, and b) the addition of mid and trackIdentifier to rtp stats, the sender/receiver/transceiver do not contain any new information. But they do have the useful property of having different lifetimes than rtp stats. As we see in #619, some people think the supposed lifetime of the rtp objects is a problem. In this issue we should decide if new dictionaries (sender/receiver/transceivers) are needed or if we should change the lifetime of the rtp stats to avoid having more dictionaries that don’t otherwise add new information. Did Firefox implement ”RTP stats lifetimes are tied to RTP” already? I know Chromium browsers have not. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/643#issuecomment-1159414586 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 18 June 2022 09:55:28 UTC