Split the policy refresh rate preference into user- and device-policy refresh rate.

chrome/browser/policy/configuration_policy_pref_store.cc

Index: chrome/browser/policy/configuration_policy_pref_store.cc
diff --git a/chrome/browser/policy/configuration_policy_pref_store.cc b/chrome/browser/policy/configuration_policy_pref_store.cc
index 96dfb2eec67b6087cb60694e2dac4ec0f381c36a..03960f802dd9262b74944203d58d57a1452bf41b 100644
--- a/chrome/browser/policy/configuration_policy_pref_store.cc
+++ b/chrome/browser/policy/configuration_policy_pref_store.cc
@@ -247,7 +247,9 @@ const ConfigurationPolicyPrefKeeper::PolicyToPreferenceMapEntry
   { Value::TYPE_BOOLEAN, kPolicyDisablePluginFinder,
     prefs::kDisablePluginFinder },
   { Value::TYPE_INTEGER, kPolicyPolicyRefreshRate,

[Mattias Nissler (ping if slow), 2011/05/13 09:45:03]

We'll run into a problem here if we use the same policy type for both prefs:
Even if we have two different sources for policy values (user and device), we'll
merge them here, which is not what we want. Adding a new policy type goes
through the autogenerated code, but I'm not sure whether we want the device
policies in the JSON template. Need to discuss this with gfeher@ I guess

[sfeuz, 2011/05/17 14:27:42]

Added a policy for the DevicePolicyRefreshRate.

[Mattias Nissler (ping if slow), 2011/05/17 14:47:03]

Ah, but then there is the problem that the autogenerated policy decoder will
also accept that setting for user policy, which is not what we want. You may
want to look at the generator and talk to jkummerow/gfeher who have built the
code generation infrastructure.

-    prefs::kPolicyRefreshRate },
+    prefs::kDevicePolicyRefreshRate },
+  { Value::TYPE_INTEGER, kPolicyPolicyRefreshRate,
+    prefs::kUserPolicyRefreshRate },
   { Value::TYPE_BOOLEAN, kPolicyInstantEnabled, prefs::kInstantEnabled },
   { Value::TYPE_BOOLEAN, kPolicyDefaultBrowserSettingEnabled,
     prefs::kDefaultBrowserSettingEnabled },