Change DeviceStatusCollector to return status asynchronously Part 2 |
||||||||||
Issue descriptionIn part 1 of this change (crbug/450523), the DeviceStatusCollector interface was refactored to return status asynchronously. However, the actual status gathering process is still synchronous. DeviceStatusCollector should be changed to gather CPU temp and drive volume info on demand instead of sampling the data in regular intervals. Geo location should be removed, it is not used. Moreover, consider using NonThreadSafe / ThreadChecker instead of the current implementation to verify that the calls happen on the correct threads.
,
Sep 28 2016
,
Sep 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6e4082c0fc2425bb6f040e29baae4362246ef93d commit 6e4082c0fc2425bb6f040e29baae4362246ef93d Author: ljusten <ljusten@chromium.org> Date: Wed Sep 28 08:12:43 2016 Refactored DeviceStatusCollector to enable truely asynchronous status queries Combined GetDeviceStatusAsync and GetDeviceSessionStatusAsync into one function. They are always called together and combining them makes StatusGetter in status_uploader.h/cc unnecessary. Added helper class to keep state for asynchronous status queries. Disk volume info and CPU temp info are now collected asynchronously when status is requested. Before, the data was sampled regularly and only the last sample was used. Removed unused geo location reporting code. Deprecated device_location field in protobuf. Changed thread-checking to use ThreadChecker class. BUG= 639372 Review-Url: https://codereview.chromium.org/2314813002 Cr-Commit-Position: refs/heads/master@{#421475} [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.cc [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/browser/chromeos/policy/device_status_collector.cc [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/browser/chromeos/policy/device_status_collector.h [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/browser/chromeos/policy/device_status_collector_browsertest.cc [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/browser/chromeos/policy/status_uploader.cc [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/browser/chromeos/policy/status_uploader.h [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/browser/chromeos/policy/status_uploader_unittest.cc [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/common/pref_names.cc [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/chrome/common/pref_names.h [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/components/policy/proto/device_management_backend.proto [modify] https://crrev.com/6e4082c0fc2425bb6f040e29baae4362246ef93d/components/policy/resources/policy_templates.json
,
Oct 7 2016
,
Nov 14 2016
,
Nov 19 2016
,
Jan 21 2017
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Jul 6 2017
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by bartfab@chromium.org
, Aug 26 2016