7f585b3c12
This will be used by WebRTC tests. It converts results exactly the same as our downstream implementation (histogram_util). This implementation should be pretty feature complete, or at least enough to start testing the end-to-end flow. I will set up some experimental recipe code and see if this actually makes it into the dashboard. Note: needs some catapult changes to land first and be rolled into Chromium, and then WebRTC. Bug: chromium:1029452 Change-Id: I939046929652fc27b8fcb18af54bde22886d9228 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/166172 Commit-Queue: Patrik Höglund <phoglund@webrtc.org> Reviewed-by: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30436}
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