PreferencesManager

services/preferences/public/interfaces/preferences.mojom

 // Copyright 2016 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.
 
 module prefs.mojom;
 
 import "mojo/common/common_custom_types.mojom";
 
+const string kServiceName = "prefs:manager";

[sadrul, 2016/12/08 01:07:22]

This is kCapabilityName, right?

[jonross, 2016/12/08 14:36:40]

I'd only seen kServiceName used in mojoms for declaring services/capabilities

[sadrul, 2016/12/08 15:33:31]

service name is the actual name of the service you use to connect to the thing,
e.g. "ui" or "catalog". In this case, 'prefs:manager' is not the name of the
service, it's the name of the capability you use in your manifest, right? I
think kCapabilityName would be a better name to clarify that. Are there other
places where we use 'service name' to refer to capability?

[jonross, 2016/12/09 20:48:03]

There currently is 0 usage of kCapabilityName. Though it does make sense to
differentiate between the two styles of connection.

[jonross, 2016/12/14 15:01:41]

Done.

+
 // Used to subscribe to preference changes within PreferenceManager. After
 // requesting to observe, the current values for all requested keys are sent.
 interface PreferencesObserver {
   OnPreferencesChanged(mojo.common.mojom.DictionaryValue preferences);
 };
 
 // Manages actual read/write of preference data. Accepts observers who subscribe
 // to preferences, notifying them of changes.
 interface PreferencesManager {
-  AddObserver(array<string> preferences, PreferencesObserver client);
+  AddObserver(PreferencesObserver client);
   SetPreferences(mojo.common.mojom.DictionaryValue preferences);
+  Subscribe(array<string> preferences);
 };