1c5e6d0a3f
I'm not sure why we ever had this in the first place, and it confuses people on a nearly weekly basis, so let's get rid of it. The protocols are enabled right after the corresponding gathering is done, so the only real effect it has is to produce confusing log messages (first "candidate not signaled because protocol not enabled", then "protocol enabled, signaling candidate" right afterwards). BUG=None Review-Url: https://codereview.webrtc.org/3018483002 Cr-Commit-Position: refs/heads/master@{#19873}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
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