- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Dec 2022 14:20:12 +0000
- To: public-webrtc-logs@w3.org
The imagined usage when we designed this interface (a year ago) was pc.setOfferedRtpHeaderExtensions([origin-timestamp: sendrecv, new-fancy-reporting: send]) with all the 14 other extensions being unchanged by the setOfferedRtpHeaderExtensions call, and an exception being thrown if new-fancy-reporting is either misspelled or unsupported. What is now being suggested is that for this use case, we need to do: ``` extensions = pc.HeaderExtensionsToOffer(); extensions.find(uri=origin-timestamp).direction = sendrecv; extensions.find(uri=new-fancy-reporting).direction = send; pc.setOfferedRtpHeaderExtensions(extensions); ```` It's easy to shim one on top of the other, but I'm hesitant to declare that the new proposal is better than the old proposal without seeing a realistic use case that is simpler with the second semantics. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/130#issuecomment-1341037233 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 December 2022 14:20:14 UTC