- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Mar 2024 09:28:04 +0000
- To: public-webrtc-logs@w3.org
> I understand we got here incrementally, but I don't see why JS is needed when we can add first-class support for fanout. AIUI, the desire is for the web page to act a little bit like an SFU. I do not think the UA will be able to implement everything that a web page could do, for instance: - Handle the case where there is bandwidth limitation (the receiver can try to do some adaptation, say if the receiver is L1T2, it might only send L1T1, switch from source...). - Handle the case where the receiver gets redundant frames from multiple paths and will forward from one of this path on a per frame basis. I think this use case was presented but @guidou probably knows more. - Handle recovery cases, like packet loss or PLI/FIR (which of the multiple potential receivers to ask for the key frame, what to do when waiting...). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/198#issuecomment-2011733915 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 March 2024 09:28:05 UTC