commit | ffbfba979f9d48176c7ed5dcc60b6a8076303b71 | [log] [tgz] |
---|---|---|
author | Jesús Leganés-Combarro 'piranna <piranna@gmail.com> | Tue May 25 08:35:10 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 03 19:24:55 2021 |
tree | 830bf98833da39234e7a1148dca48eb7d3dc3742 | |
parent | 1050fbca91e7685e42cf97d3fa11cf6beac96eb7 [diff] |
Added `PeerConnectionObserverJni::OnRemoveTrack()` Change-Id: I0880caa77a1097f56c560152e85c9ca29242f825 This PR add support for the `PeerConnectionObserverJni::OnRemoveTrack()` event on Java, allowing to be notified when a remote track has been removed. It's a very thing JNI wrapper on top of C++ API, being mostly similar to other already available events like `track` and `addTrack`. In Javascript API, tracks are not "removed" explicitly from the PeerConnection, but instead receiver PeerConnection gets notified that they have been removed from the streams they are associated to, and when no `MediaStream` object has that track, it's considered that the track has been removed from the PeerConnection. In Java and C++ APIs there's no `MediaStreamObserver` class, so there's no way to listen to the `removeTrack` event the same way happens in Javascript API, but instead C++ API has a `removeTrack` event at PeerConnection level. This patchset just only wraps and expose this `removeTrack` event from the C++ API to the Java API. This PR has been sponsored by Atos Research and Innovation (https://atos.net/en/about-us/innovation-and-research). Bug: webrtc:12850 Change-Id: I0880caa77a1097f56c560152e85c9ca29242f825 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/218847 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Xavier Lepaul <xalep@webrtc.org> Commit-Queue: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34225}
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.