Move user cloud policy to BrowserProcess (was 6979011)

chrome/browser/policy/device_policy_cache.cc

Index: chrome/browser/policy/device_policy_cache.cc
diff --git a/chrome/browser/policy/device_policy_cache.cc b/chrome/browser/policy/device_policy_cache.cc
index bb9f5339146baade3d10c68e1751dbd27db7f0dd..56811c337a6f677ba2b0a7ab383cf7dc0df70ee7 100644
--- a/chrome/browser/policy/device_policy_cache.cc
+++ b/chrome/browser/policy/device_policy_cache.cc
@@ -181,6 +181,10 @@ void DevicePolicyCache::SetUnmanaged() {
   // This is not supported for DevicePolicyCache.
 }
 
+bool DevicePolicyCache::IsReady() {

[Mattias Nissler (ping if slow), 2011/06/24 17:27:17]

Hm, now we have IsReady() and initialization_complete(), of which we effectively
use only one, correct? If so, I'd prefer to change the semantics of
initialization_complete() as required.

[gfeher, 2011/06/27 16:50:24]

They actually do mean two different things:
initialization_complete(): we've got a usable policy response either from the
cache/disk storage or from the network
IsReady(): initialization_complete() OR the local disk storage was checked (but
it may have been empty or otherwise corrupted)

initialization_complete() is used for several things:
- in user_policy_cache.cc: avoiding overriding the fresh policy from network
with an old policy from the cache
- in cloud_policy_cache_base.h: determining if the cache has policy or not

I'll make the method protected and improve comments.

+  return initialization_complete() || !starting_up_;
+}
+
 void DevicePolicyCache::OnRetrievePolicyCompleted(
     chromeos::SignedSettings::ReturnCode code,
     const em::PolicyFetchResponse& policy) {