839439ae84
The spec says: "Represents the total number of connectivity check requests sent (not including retransmissions)." I was surprised to find candidate-pair.requestsSent wired up to `sent_ping_requests_before_first_response`, which is the subset of `sent_ping_requests_total` that happened when `recv_ping_responses` was 0. This is not what the spec says. By wiring it up to `sent_ping_requests_total` instead, the modern getStats implementation of "requestsSent" will match the legacy getStats implementation which is already wired up to this value. // Unrelated bot issues NOTRY=True Bug: webrtc:14425 Change-Id: Ia53c9711ee7a13e596ae0eacf6066b97d9a1face Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/274174 Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/main@{#38025}
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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation