00f4fd9b1a
This also deletes unused method has_channels() and moves us closer to having the ChannelManager just be a factory class. Once we get there the ownership of the channels themselves can be with the classes that hold pointers to them. Today the initialization and teardown of those classes need to be synchronized with ChannelManager. But there's no real value in keeping the channel pointers owned elsewhere. Places where we have naked un-owned channel pointers: * RtpTransceiver for voice and video * PeerConnection::data_channel_controller_ (rtp data channel) Bug: webrtc:11994 Change-Id: Id6df27414cc57b6ecf0f7f769fdb9603ed114bfd Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/214440 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33654}
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