commit | 9438ddc9fc6bddeb7409e8a24827c8ed06c2a9ee | [log] [tgz] |
---|---|---|
author | Henrik Boström <hbos@webrtc.org> | Mon May 11 14:32:41 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Mon May 11 21:39:40 2020 |
tree | 38e0c97f4b49bf338fcdcf1d35b82364605358f7 | |
parent | f9ed56b656fbef32ff5d8a26a25c7411d2292529 [diff] |
[Adaptation] Give QualityScaler a pending callbacks queue and unittests This CL adds a queue for pending QualityScalerQpUsageHandlerCallbacks and private methods for "Queueing", "Handling" and "Aborting" them, using a sequence number as an ID to ensure we don't accidentally invoke the same callback twice. Because we don't have the adaptation task queue yet, callbacks are still synchronously handled, which means the "pending callbacks" queue would never have more than 1 element. However, when the adaptation task queue is added and this is made asynchronous, it will be possible for multiple callbacks to be pending simultaneously. This design is future-proof. This CL is split out to aid reviewability. The CL that adds the adaptation task queue will affect a lot of code. By landing this separately, the adaptation queue CL will be easier to review. This CL adds quality_scaler_resource_unittest.cc. Bug: webrtc:11542, webrtc:11520 Change-Id: I00e7f6bfda9f8e8e82ec25916aa48e9349c8d70c Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/174802 Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Evan Shrubsole <eshr@google.com> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31219}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.