Extract common per-network proxy configuration functions.

chrome/browser/chromeos/net/proxy_config_handler.h

Index: chrome/browser/chromeos/net/proxy_config_handler.h
diff --git a/chrome/browser/chromeos/net/proxy_config_handler.h b/chrome/browser/chromeos/net/proxy_config_handler.h
new file mode 100644
index 0000000000000000000000000000000000000000..7e87298018adeea8a4a20f5b9aad79239b9e0ba6
--- /dev/null
+++ b/chrome/browser/chromeos/net/proxy_config_handler.h
@@ -0,0 +1,27 @@
+// Copyright (c) 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_CHROMEOS_NET_PROXY_CONFIG_HANDLER_H_
+#define CHROME_BROWSER_CHROMEOS_NET_PROXY_CONFIG_HANDLER_H_
+
+#include "base/memory/scoped_ptr.h"
+#include "chromeos/network/network_state.h"
+
+class ProxyConfigDictionary;
+
+namespace chromeos {
+
+namespace proxy_config {
+
+scoped_ptr<ProxyConfigDictionary> GetProxyConfigOfNetwork(

[stevenjb, 2013/06/06 18:21:12]

nit: s/Of/For
Also, should these have success / error callbacks like the
NetworkConfigurationHandler functions? It seems like it would be more
consistent, and something we should handle in the future, even if they are
currently NULL.

[pneubeck (no reviews), 2013/06/07 09:46:10]

I agree, that we should go in that direction.
However, as these callbacks wouldn't be used, I'd like to postpone that change
and avoid yet another bunch of calls in the kind of:
 handler->Set...(
        ...
        chromeos::network_handler::ErrorCallback());

These are already all over the place.

+    const NetworkState& network);
+
+void SetProxyConfigOfNetwork(const ProxyConfigDictionary& proxy_config,
+                             const NetworkState& network);

[stevenjb, 2013/06/06 18:21:12]

Here too

[pneubeck (no reviews), 2013/06/07 09:46:10]

Done.

+
+}  // namespace proxy_config
+
+}  // namespace chromeos
+
+#endif  // CHROME_BROWSER_CHROMEOS_NET_PROXY_CONFIG_HANDLER_H_