webrtc

Files

jiayl@webrtc.org dacdd9403d Reland r7980:

Accept incoming pings before remote answer is set, to reduce connection latency.
Set ICE connection state to 'checking' after setting the remote answer, so that it can transition into 'connected' if the peer reflexive connection is up before any remote candidate is set. See more details in crbug/446908

BUG=4068, crbug/446908
R=juberti@webrtc.org, pthatcher@webrtc.org

Review URL: https://webrtc-codereview.appspot.com/38709004

git-svn-id: http://webrtc.googlecode.com/svn/trunk@8141 4adac7df-926f-26a2-2b94-8c16560cd09d

2015-01-23 17:33:34 +00:00

android/org/webrtc

Update libjingle license statements at top of talk files for consistency

2015-01-20 21:36:13 +00:00

jni

Correct the class name in peerconnection_jni.cc.

2015-01-21 07:57:06 +00:00

src/org/webrtc

Update libjingle license statements at top of talk files for consistency

2015-01-20 21:36:13 +00:00

testcommon/src/org/webrtc

Reland r7980:

2015-01-23 17:33:34 +00:00

README

Adds trunk/talk folder of revision 359 from libjingles google code to

2013-07-10 00:45:36 +00:00

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, build with 
OS=linux or OS=android and include
build_with_libjingle=1 build_with_chromium=0
in $GYP_DEFINES.

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 jni/.

An example command-line to build & run the unittest:
cd path/to/trunk
GYP_DEFINES="build_with_libjingle=1 build_with_chromium=0 java_home=path/to/JDK" gclient runhooks && \
    ninja -C out/Debug libjingle_peerconnection_java_unittest && \
    ./out/Debug/libjingle_peerconnection_java_unittest
(where path/to/JDK should contain include/jni.h)

During development it can be helpful to run the JVM with the -Xcheck:jni flag.