bc32c56f83
A pointer to the transport controller is now maintained on both the network thread and the signaling thread. We use thread specific accessors to make it explicit which copy we are accessing at any given time. We also move the initial offerer value to the SDP offer/answer class; this is determined on the basis of SDP offer/answer, so there is no need to hop to the network thread for that. Work in progress. Bug: webrtc:9987 Change-Id: Idbe5a7fbf44f667adcd119e486133cf6e43ab1f5 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/251382 Reviewed-by: Tomas Gunnarsson <tommi@webrtc.org> Commit-Queue: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35965}
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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation