018dd6e9d1
The reasons behind this change: 1. In OpenSSL 1.1.0. BIO will be an opaque object. We won't have direct access to the `num` field. 2. `num` is only used by OpenSSL provided BIOs and different types of BIOs use num differently. WebRTC is providing its own customized BIO implementation, it probably shouldn't piggyback into this internal field to store the stream/socket state. 4. We can access the stream/socket state directly using the underlying object anyway. Bug: webrtc:8817 Change-Id: I41cdd2920fba378e312e8436a7b9733381555522 Reviewed-on: https://webrtc-review.googlesource.com/46360 Commit-Queue: Jiawei Ou <ouj@fb.com> Reviewed-by: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21814}
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