commit | e95b57cdfc4a4deb9e15363adfb18eff736e3230 | [log] [tgz] |
---|---|---|
author | Mirko Bonadei <mbonadei@webrtc.org> | Fri Jul 12 14:55:42 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jul 12 15:27:19 2019 |
tree | 2d5221e31d18c7ddc73e318bcfc00bcb406fcef7 | |
parent | 2c850afe8d0fd427c159b0280ff2c140f2f72eb7 [diff] |
Revert "Remove the injectable bitrate allocation strategy API." This reverts commit 80cb3f6db622442b6360e67851e8903aa0d06d03. Reason for revert: Performance regression on downstream project. Original change's description: > Remove the injectable bitrate allocation strategy API. > > This removes PeerConnectionInterface::SetBitrateAllocationStrategy() > plus a ton of now-dead code. > > Bug: webrtc:10556 > Change-Id: Icfae3bdd011588552934d9db4df16000847db7c3 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/133169 > Reviewed-by: Henrik Andreassson <henrika@webrtc.org> > Reviewed-by: Niels Moller <nisse@webrtc.org> > Reviewed-by: Sebastian Jansson <srte@webrtc.org> > Commit-Queue: Jonas Olsson <jonasolsson@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#28523} TBR=henrika@webrtc.org,kwiberg@webrtc.org,nisse@webrtc.org,srte@webrtc.org,alexnarest@webrtc.org,jonasolsson@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: webrtc:10556 Change-Id: Ife905d661e7b1a227662395c729a9336c62fd2d7 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/145338 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28560}
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.
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.