- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Dec 2023 08:24:24 +0000
- To: public-webrtc-logs@w3.org
Status: This PR has been languishing for 3 months now. The addition of a pure "sendonly" API is under consideration, but seems to require more time (#211), and the discussion so far has not shown a compelling difference from the interface that is effectively created if you don't attach a sending track to a transceiver. The use case for forwarding has been accepted. No use case where the restriction serves a positive purpose (enabling an use case) has been described; the only argument put forward is that it gives the opportunity to fire an error when people try unexpected things. We should consider again whether we should remove the restriction from the spec. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/201#issuecomment-1859760193 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 December 2023 08:24:26 UTC