ddcfb9fc6a
The pacer has a mechanism to make sure all packets are sent within some time limit. This is based on the average queue time of the packets in the pacer queue. If the pacer is paused while packets are still in the queue (for instance if the underlying transport goes down temporarily), on resume all those packets might be past the time limit and thus will all be burst out onto the network in a tight loop. This CL subtracts pause time from the queue time, effectively pausing the clock for the queue while the pacer is paused, so that when we resume the pacing bitrate will be the same as when we paused. BUG=webrtc:7694 Review-Url: https://codereview.webrtc.org/2994323002 Cr-Commit-Position: refs/heads/master@{#19367}
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- 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