681de2036b
With the current implementation, whenever we are toggling between sending/not sending retransmissions, the BitrateAllocator will toggle the total requested max bitrate that is signalled to the probing mechanism. The result is that spurious probes are sent mid-call, at |max_bitrate| and |2*max_bitrate|. This behaviour is undesirable, and thus removed in this CL. Instead, whenever the allocation limits actually change, we produce a single set of probes at |max_bitrate| and |2*max_bitrate|. This CL does not change how the BitrateAllocator hysteresis is accounting for protection, since it does not relate to the spurious probes. Bug: webrtc:10275 TBR: sprang@webrtc.org Change-Id: Iab3a690a500372c74772a8ad6217fb838af15ade Reviewed-on: https://webrtc-review.googlesource.com/c/120808 Commit-Queue: Rasmus Brandt <brandtr@webrtc.org> Reviewed-by: Sebastian Jansson <srte@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26544}
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