- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Aug 2022 15:21:05 +0000
- To: public-webrtc-logs@w3.org
> @docfaraday mentioned offline a similar issue with addTrack and SRD(simulcastOffer). After more offline discussion, it seems like this particular question (what to do when setParameters races against sRD(simulcast offer)) depends on what the expected behavior is in the non-racy case. So if JS calls addTrack, then performs a get/setParameters cycle (which will have one encoding), what should be done with a subsequent sRD(simulcast offer)? Do we interpret the unicast get/setParameters cycle as establishing unicast, and reject the simulcast in our answer? Do we have the sRD(simulcast offer) stomp the encodings entirely? Or do we try to merge the two parameter sets somehow? -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2737#issuecomment-1216785363 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 August 2022 15:21:06 UTC