d48a2b14e7
This moves the thread hop for network events, from BaseChannel and into Call. The reason for this is to move the control over those hops (including DeliverPacket[Async]) into the same class where the state is held that is affected by those hops. Once that's done, we can start moving the relevant network state over to the network thread and eventually remove the hops. I'm also adding several TODOs for tracking future steps and give developers a heads up. Bug: webrtc:11993 Change-Id: Ice7ee3b5b6893532df52039324293979196d341d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/204800 Commit-Queue: Tommi <tommi@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33138}
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