wifi_sync: add function to create a network in Shill

components/wifi_sync/network_state_helper_chromeos.h

Index: components/wifi_sync/network_state_helper_chromeos.h
diff --git a/components/wifi_sync/network_state_helper_chromeos.h b/components/wifi_sync/network_state_helper_chromeos.h
index 5163ee3e105d90fdeff1b031b77191a7ba27940d..33ae018a2c8589b03cdfabf94b4536086a4deb7a 100644
--- a/components/wifi_sync/network_state_helper_chromeos.h
+++ b/components/wifi_sync/network_state_helper_chromeos.h
@@ -7,14 +7,29 @@
 
 #include <string>
 
+#include "chromeos/network/network_handler_callbacks.h"
 #include "components/wifi_sync/wifi_credential.h"
 
 namespace chromeos {
+class ManagedNetworkConfigurationHandler;
 class NetworkStateHandler;
 }
 
 namespace wifi_sync {
 
+// Adds a local network configuration entry for a WiFi network using
+// the properties of |wifi_credential|. The network configuration
+// entry is added to the Shill profile for |user_hash|. If the entry
+// already exists, the call fails. The call always completes
+// asynchronously, invoking |success_callback| or |error_callback| as

[erikwright (departed), 2015/01/07 20:07:14]

using what thread/message loop/task runner?

[mukesh agrawal, 2015/01/07 22:14:18]

AIUI, the callback will be executed using the origin_task_runner_ of dbus::Bus.
That executes tasks on the dbus::Bus "origin thread". Per the documentation for
dbus::Bus, the origin thread is the one "that created the Bus object", and is
"usually Chrome's UI thread".

stevenjb: Please confirm or correct my understanding.
erikwright: For the function's documentation, would it be better to simply say
that the callbacks usually execute on the UI thread? Or should I give a fuller
explanation?

+// appropriate.
+void CreateWifiNetworkInShillUserProfile(
+    chromeos::ManagedNetworkConfigurationHandler* managed_net_config_handler,
+    const std::string& user_hash,
+    const WifiCredential& wifi_credential,
+    const chromeos::network_handler::StringResultCallback& success_callback,
+    const chromeos::network_handler::ErrorCallback& error_callback);
+
 // Returns a platform-agnostic representation of the ChromeOS network
 // configuration state. The configuration state is filtered, so that
 // only items related to ChromeOS |shill_profile_path| are returned.