bb7727211c
The (currently unused) new pacer code path was implemented with what was intended as a more careful padding strategy. Unfortunately this doesn't work as well as expected due to the fact that the padding budget cannot build up underuse. I made another CL that could fix that, but I think it adds complexity for dubious gains. It also will make it more difficult to find any potential regression when switching to the new path, should one occur. See https://webrtc-review.googlesource.com/c/src/+/144563 Therefore, this CL makes the new code path choose RTX payload in the same way as is currently done. Bug: webrtc:10633 Change-Id: If2115d4fa7463add959faa77c63101286c27e0f5 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/145202 Reviewed-by: Stefan Holmer <stefan@webrtc.org> Commit-Queue: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28537}
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