summaryrefslogtreecommitdiff
path: root/update_manager/update_manager_unittest.cc
diff options
context:
space:
mode:
authorGilad Arnold <garnold@chromium.org>2014-10-28 15:57:30 -0700
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2014-11-12 02:42:43 +0000
commit4a0321b804524e001b482edea882bd1fc4af98a2 (patch)
tree896826dca671af3a0cd712ef7aa408349daea04e /update_manager/update_manager_unittest.cc
parent020600db42428e7e96bb0d2e05da225e68650955 (diff)
update_engine: Policy determines P2P enabled status.
This switches the P2P Manager to use the newly introduced Update Manger policy requests in determining whether P2P is enabled on the system. There is a policy request for the initial state (P2PEnabled, sync) and for tracking changes (P2PEnabledChanged, async), with the latest known value being cached by the P2P Manager. This also reverses a recent change that moved P2P prefs setting into the P2PManager. In the absence of any additional logic (now cleared) there was no point in having a dedicated method just for that, and so dbus_service writes the prefs value directly. This affords us removing the prefs argument when initializing the P2PManager. BUG=chromium:425233 TEST=Unit tests. Change-Id: I53280f05da8fe532b6502c175a8cc9ddc1e15a87 Reviewed-on: https://chromium-review.googlesource.com/226937 Tested-by: Gilad Arnold <garnold@chromium.org> Reviewed-by: David Zeuthen <zeuthen@chromium.org> Commit-Queue: Gilad Arnold <garnold@chromium.org>
Diffstat (limited to 'update_manager/update_manager_unittest.cc')
0 files changed, 0 insertions, 0 deletions