Use a service to create device management backends.

chrome/browser/profile.h

Index: chrome/browser/profile.h
diff --git a/chrome/browser/profile.h b/chrome/browser/profile.h
index f76a2732680547930b7f74c59e9acd8f2fcb8242..b373faf3bcec59a520c1c08a29f41a088ccdd3dc 100644
--- a/chrome/browser/profile.h
+++ b/chrome/browser/profile.h
@@ -31,6 +31,7 @@ class SSLConfigService;
 }
 
 namespace policy {
+class DeviceManagementService;
 class DeviceManagementPolicyProvider;
 }
 
@@ -476,6 +477,9 @@ class Profile {
   // Returns the PromoCounter for Instant, or NULL if not applicable.
   virtual PromoCounter* GetInstantPromoCounter() = 0;
 
+  // Gets the device management service associated with this profile.
+  virtual policy::DeviceManagementService* GetDeviceManagementService() = 0;

[Nico, 2010/11/18 15:36:33]

Do you think it might be worth it to have a PolicyProvider class which contains
"all" this policy stuff (currently just DeviceManagementService and
DeviceManagementPolicyProvider), so that the profile has only one accessor for
all the policy stuff?

[Mattias Nissler (ping if slow), 2010/11/19 16:03:56]

That is definitely worthwile. I created a new PolicyContext class that bundles
all the bits and has nice accessors.

+
   // Get the device management policy provider for this profile.
   virtual policy::DeviceManagementPolicyProvider*
       GetDeviceManagementPolicyProvider() = 0;