- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Apr 2021 15:35:16 +0000
- To: public-webrtc-logs@w3.org
The purpose of the signaling mechanism is to expose communication from sinks to sources that may be occurring. For example, in Chromium, a Peer Connection sometimes internally requests a frame from the source as part of its internal implementation. It also sends other feedback to capturers. Some sources ignore this feedback and others act on it. An implementation is not required to do these things, but it can do them in order to, for example, optimize performance. What the signaling mechanism allows is to expose this to custom sources and sinks. A source (e.g., the writable of a MediaStreamTrackGenerator ) can ignore a request for a frame if it doesn't make sense for it. So, to answer your questions. 1. No. Specs shouldn't define when native sinks need to create such signals. A native implementation of a sink may send them if it makes sense, but it is not required to. 2. Signals can be ignored since not all sources (platform or JS) are required to act on them. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/24#issuecomment-829342016 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 April 2021 15:35:18 UTC