8cb9706288
SdpOfferAnswerHandler now hands over most of the work of adding a remote candidate over to PeerConnection where the work will be carried out asynchronously on the network thread (was synchronous/blocking). Once added, reporting (ReportRemoteIceCandidateAdded) continues on the signaling thread as before. The difference is though that we don't block the UseCandidate() operation which is a part of applying the local and remote descriptions. Besides now being asynchronous, there's one behavioural change: Before starting the 'add' operation, the validity of the candidate instance to be added, is checked. Previously if such an error occurred, the error was silently ignored. Bug: webrtc:9987 Change-Id: Ic1bfb8e27670fc81038b6ccec95ff36c65d12262 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/206063 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33230}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct
- Reporting bugs