d2a1f09b18
Today OnResourceOveruse() and OnResourceUnderuse() implicitly checks preconditions and if they pass calculate the next target, and if those are usable it applies them to the VideoSourceRestrictions. These are two big "MaybeAdapt" methods. This CL takes us one step closer to "GetNextTarget", "CanApplyTarget?" and "DoApplyTarget!"-logic, which will allow us to more easily evaluate a multitude of alternative configurations and decide which one to pick (e.g. multi-stream adaptation). But it does not take us all the way there. In this CL we have: - CanAdaptUp, CanAdaptDown: This covers *most* of the preconditions. - OnResourceUnderuse, OnResourceOveruse: This aborts if CanAdapt returns false. If they pass, we calculate the next target and maybe-adapt it. This is roughly outlined in document still in draft: https://docs.google.com/document/d/1YMg-AycFZR1DS6hEav9OzJ3hqxFil09qPhlTAgQrU1g/edit?usp=sharing. A future CL should make the target more explicit and we should know if the target can be applied before we even try. Bug: webrtc:11222 Change-Id: If18d9572884aa6ba2350e4670a1516da5835cc98 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168721 Reviewed-by: Evan Shrubsole <eshr@google.com> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30605}
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