commit | e1223747c27e22c4c4c3006af10d58aec9718b28 | [log] [tgz] |
---|---|---|
author | Salman Malik <salmanmalik@google.com> | Wed Mar 23 23:50:48 2022 +0000 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 24 17:53:53 2022 +0000 |
tree | d6471be8dd5376c7f24820065863827c84f19a11 | |
parent | ed4a5763f825b911978d2552554baaf14046cdf2 [diff] |
wayland: Add a common interface for screencast and remote desktop portal Change adapts the `base_capturer_pipewire` so that a portal can be injected in the capturer. This allows the remoting to inject its own portal for the purpose of capturing desktop stream as long as the injected portal provides implementation of the new interface that is added as part of this change. Additionally, a method has been exposed on the capturer to get details about the portal session so that the remoting implementation can use the same underlying session for controlling inputs on the remote host. Finally, desktop capturer interface is extended with a generic method `GetMetadata` that is used to retrieve session related information by CRD and relay it over to its input injector. Clients provide override for the method and it eventually invokes the underlying `GetSessionDetails` method on the portal instance. Bug: chromium:1291247 Change-Id: I81b7ce3b949d8be2e24e2d303d5fbc76a849209c Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/256400 Reviewed-by: Alexander Cooper <alcooper@chromium.org> Commit-Queue: Salman Malik <salmanmalik@google.com> Cr-Commit-Position: refs/heads/main@{#36323}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.