9a2e32b9f2
And the same for outstanding items, which become unacked items. The old names were unfortunate - especially since they were managed by a class called OutstandingData. To make this less complicated, these variables have been renamed to something that is easier to understand; "Unacked bytes/items". Simply what has been sent but hasn't been acked or nacked yet. So likely what's in-flight, but could possibly be lost and not found to be lost yet. Bug: None Change-Id: I877d7f2cac5d164bf2f9f66cb32ae1f6d850ad2c Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/329761 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#41313}
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