Signed settings refactoring: Proper caching and more tests.

chrome/browser/chromeos/login/signed_settings.h

Index: chrome/browser/chromeos/login/signed_settings.h
diff --git a/chrome/browser/chromeos/login/signed_settings.h b/chrome/browser/chromeos/login/signed_settings.h
index 4e6b79f5538093dd625175d9cd365b82f729e165..8790ffb231bc487173023f9a08afa88de6527ee1 100644
--- a/chrome/browser/chromeos/login/signed_settings.h
+++ b/chrome/browser/chromeos/login/signed_settings.h
@@ -13,17 +13,9 @@
 #include "base/memory/ref_counted.h"
 #include "chrome/browser/chromeos/login/owner_manager.h"
 
-// There are two categories of operations that can be performed on the
-// Chrome OS owner-signed settings store:
-// 1) doing stuff to the whitelist (adding/removing/checking)
-// 2) Storing/Retrieving arbitrary name=value pairs
+// There are two operations that can be performed on the Chrome OS owner-signed
+// settings store: Storing and Retrieving the policy blob.

[Mattias Nissler (ping if slow), 2011/11/30 11:22:44]

Now that this is much simpler, is it still useful to have both SignedSettings
and SignedSettingsHelper? Should we rewrite these two as well? Certainly not in
this CL though?

[pastarmovj, 2011/11/30 17:21:16]

Maybe if we rename the SignedSettingsHelper to SignedSettingsQueue it will
represent better what it does. It really only helps us queue operations and
ensure consistency this way.

 //
-// Unfortunately, it is currently a limitation that only one of each
-// category can be in-flight at a time.  You can be doing exactly one thing
-// to the whitelist, and exactly one thing to the property store at a time.
-// I've filed an issue on me to remove that restriction.
-// http://code.google.com/p/chromium-os/issues/detail?id=6415
-
 // The pattern of use here is that the caller instantiates some
 // subclass of SignedSettings by calling one of the create
 // methods. Then, call Execute() on this object from the UI
@@ -44,6 +36,8 @@ namespace em = enterprise_management;
 namespace chromeos {
 class OwnershipService;
 
+extern const char kDevicePolicyType[];
+
 class SignedSettings : public base::RefCountedThreadSafe<SignedSettings>,
                        public OwnerManager::Delegate {
  public:
@@ -65,17 +59,6 @@ class SignedSettings : public base::RefCountedThreadSafe<SignedSettings>,
   SignedSettings();
   virtual ~SignedSettings();
 
-  // These are both "property" operations, and only one instance of
-  // one type can be in flight at a time.
-  static SignedSettings* CreateStorePropertyOp(
-      const std::string& name,
-      const base::Value& value,
-      SignedSettings::Delegate<bool>* d);
-
-  static SignedSettings* CreateRetrievePropertyOp(
-      const std::string& name,
-      SignedSettings::Delegate<const base::Value*>* d);
-
   // These are both "policy" operations, and only one instance of
   // one type can be in flight at a time.
   static SignedSettings* CreateStorePolicyOp(
@@ -101,34 +84,12 @@ class SignedSettings : public base::RefCountedThreadSafe<SignedSettings>,
 
   void set_service(OwnershipService* service) { service_ = service; }
 
-  void TryToFetchPolicyAndCallBack();
-
   OwnershipService* service_;
 
  private:
   friend class SignedSettingsTest;
   friend class SignedSettingsHelperTest;
 
-  class Relay
-      : public SignedSettings::Delegate<const em::PolicyFetchResponse&> {
-   public:
-    // |s| must outlive your Relay instance.
-    explicit Relay(SignedSettings* s);
-    virtual ~Relay();
-    // Implementation of SignedSettings::Delegate
-    virtual void OnSettingsOpCompleted(
-        SignedSettings::ReturnCode code,
-        const em::PolicyFetchResponse& value) OVERRIDE;
-   private:
-    SignedSettings* settings_;
-    DISALLOW_COPY_AND_ASSIGN(Relay);
-  };
-
-  // Format of this string is documented in device_management_backend.proto.
-  static const char kDevicePolicyType[];
-
-  scoped_ptr<Relay> relay_;
-  scoped_refptr<SignedSettings> polfetcher_;
   DISALLOW_COPY_AND_ASSIGN(SignedSettings);
 };