61c5cc8eb5
OpenSSL implementations are all final implementations of their more abstract SSL variants. This should be both documented and enforced by the use of the final keyword to indicate to future WebRTC contributors that this is the intended depth of inheritance and it shouldn't be extended again. Hopefully this minor change will help keep the code simpler to maintain going forward. Bug: webrtc:9860 Change-Id: Ie22de722214e3b209c3d7727a93ac819c112434e Reviewed-on: https://webrtc-review.googlesource.com/c/108203 Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Commit-Queue: Benjamin Wright <benwright@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25401}
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.
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