Add ManagedUserSharedSettingsService.

chrome/browser/managed_mode/managed_user_shared_settings_service_factory.h

Index: chrome/browser/managed_mode/managed_user_shared_settings_service_factory.h
diff --git a/chrome/browser/managed_mode/managed_user_shared_settings_service_factory.h b/chrome/browser/managed_mode/managed_user_shared_settings_service_factory.h
new file mode 100644
index 0000000000000000000000000000000000000000..4e1be582cc0a7aff1208d635e1349ceb96a6dd7f
--- /dev/null
+++ b/chrome/browser/managed_mode/managed_user_shared_settings_service_factory.h
@@ -0,0 +1,33 @@
+// Copyright 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_BROWSER_MANAGED_MODE_MANAGED_USER_SHARED_SETTINGS_SERVICE_FACTORY_H_
+#define CHROME_BROWSER_MANAGED_MODE_MANAGED_USER_SHARED_SETTINGS_SERVICE_FACTORY_H_
+
+#include "base/memory/singleton.h"
+#include "chrome/browser/managed_mode/managed_users.h"
+#include "components/browser_context_keyed_service/browser_context_keyed_service_factory.h"
+
+class ManagedUserSharedSettingsService;
+
+class ManagedUserSharedSettingsServiceFactory
+    : public BrowserContextKeyedServiceFactory {
+ public:
+  static ManagedUserSharedSettingsService* GetForBrowserContext(
+      content::BrowserContext* profile);
+
+  static ManagedUserSharedSettingsServiceFactory* GetInstance();
+
+ private:
+  friend struct DefaultSingletonTraits<ManagedUserSharedSettingsServiceFactory>;
+
+  ManagedUserSharedSettingsServiceFactory();
+  virtual ~ManagedUserSharedSettingsServiceFactory();
+
+  // BrowserContextKeyedServiceFactory:
+  virtual BrowserContextKeyedService* BuildServiceInstanceFor(
+      content::BrowserContext* profile) const OVERRIDE;
+};

[Pam (message me for reviews), 2014/01/08 10:30:40]

Do you need to override GetBrowserContextToUse, to handle incognito?

[Bernhard Bauer, 2014/01/08 11:42:04]

I don't think so. By default, the service will be NULL for an incognito profile,
which should be fine, right?

[Pam (message me for reviews), 2014/01/08 12:19:28]

For the currently planned settings, yes, but I could see it being confusing if
some other setting is added later, especially since the non-shared settings
forward from Incognito to normal.

[Bernhard Bauer, 2014/01/08 12:59:42]

I'm not even sure anymore why we do that. For shared settings, if a client in
the future will want to get a ManagedUserSharedSettingsService for an incognito
profile, it can add the redirection. If we want to make it consistent with the
non-shared version, I'd be in favor of removing the redirection there.

+
+#endif  // CHROME_BROWSER_MANAGED_MODE_MANAGED_USER_SHARED_SETTINGS_SERVICE_FACTORY_H_