7875c99e82
This refactors the usage of OveruseFrameDetector in OveruseFrameDetectorResourceAdaptationModule into an inner class of the module, making the interaction between the detector and the module the responsibility of this helper class instead. Similarly, QualityScaler usage is moved into QualityScalerResource. This takes us one step closer to separate the act of detecting overuse/underuse of a resource and the logic of what to do when overuse/underuse happens. Follow-up CLs should build on this in order to materialize the concept of having resources, streams and a central decision-maker deciding how to reconfigure the streams based on resource usage state. Bug: webrtc:11222 Change-Id: I99a08a42218a871db8f477f31447a6379433ad05 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168057 Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Evan Shrubsole <eshr@google.com> Reviewed-by: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30468}
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