mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-17 07:37:51 +01:00
![]() 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} |
||
---|---|---|
.. | ||
api/org/webrtc | ||
instrumentationtests | ||
native_api | ||
native_unittests | ||
src | ||
tests | ||
AndroidManifest.xml | ||
BUILD.gn | ||
OWNERS | ||
PRESUBMIT.py | ||
README |
This directory holds a Java implementation of the webrtc::PeerConnection API, as well as the JNI glue C++ code that lets the Java implementation reuse the C++ implementation of the same API. To build the Java API and related tests, make sure you have a WebRTC checkout with Android specific parts. This can be used for linux development as well by configuring gn appropriately, as it is a superset of the webrtc checkout: fetch --nohooks webrtc_android gclient sync You also must generate GN projects with: --args='target_os="android" target_cpu="arm"' More information on getting the code, compiling and running the AppRTCMobile app can be found at: https://webrtc.org/native-code/android/ To use the Java API, start by looking at the public interface of org.webrtc.PeerConnection{,Factory} and the org.webrtc.PeerConnectionTest. To understand the implementation of the API, see the native code in src/jni/pc/.