1a3859c161
Update the |cumulative_lost_| counter per received packet. The rules follow from RFC 3550 and are fairly simple: Decrement the counter by one for every received packet. For every in-order packet, i.e., increasing |received_seq_max_|, add that change to |cumulative_lost_|. Net change is zero as long as packets are received in proper sequence. This way, GetStats() always returns an up-to-date value, independent of the timing of RTCP report blocks. For RTCP reports, keep a workaround to never report negative cumulative loss. Bug: webrtc:10679 Change-Id: I47ff3bf266ff2382f405ec9828d34f7fad7068b4 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/150641 Commit-Queue: Niels Moller <nisse@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29058}
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