components: add wifi_sync component

components/wifi_sync/wifi_credential_syncable_service_factory.cc

+// Copyright 2014 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.
+
+#include "components/wifi_sync/wifi_credential_syncable_service_factory.h"
+
+#include "chrome/browser/profiles/profile.h"
+#include "components/keyed_service/content/browser_context_dependency_manager.h"
+#include "components/wifi_sync/wifi_credential_syncable_service.h"
+
+namespace wifi_sync {
+
+// static
+WifiCredentialSyncableService*
+WifiCredentialSyncableServiceFactory::GetForProfile(Profile* profile) {
+  return static_cast<WifiCredentialSyncableService*>(
+      GetInstance()->GetServiceForBrowserContext(profile, true));
+}
+
+// static
+WifiCredentialSyncableServiceFactory*
+WifiCredentialSyncableServiceFactory::GetInstance() {
+  return Singleton<WifiCredentialSyncableServiceFactory>::get();
+}
+
+WifiCredentialSyncableServiceFactory::WifiCredentialSyncableServiceFactory()
+    : BrowserContextKeyedServiceFactory(
+        "WifiCredentialSyncableService",
+        BrowserContextDependencyManager::GetInstance()) {
+}
+
+WifiCredentialSyncableServiceFactory::~WifiCredentialSyncableServiceFactory() {
+}
+
+KeyedService* WifiCredentialSyncableServiceFactory::BuildServiceInstanceFor(
+    content::BrowserContext* context) const {
+  // TODO(quiche): Figure out if this behaves properly for multi-profile.
+  // crbug.com/430681.

[stevenjb, 2014/11/12 21:30:44]

Hmm, we probably need to add a helper method to src/chromeos/login to return the
"primary" browser context so that we can compare that to |context| and assert or
return nullptr for a non-primary context.

[mukesh agrawal, 2014/11/13 16:24:59]

I'd guess that asserting is too strong, because its probably normal for sync to
run for the secondary profiles in a multi-profile session. (Incognito windows
would be a different story -- sync simply shouldn't be running for incognito.)
But returning nullptr seems reasonable.

For determining the primary browser context, could we use
chromeos::ProfileHelper::IsPrimaryProfile()? 

[stevenjb, 2014/11/13 22:55:35]

Unfortunately ProfileHelper is in src/chrome so we can't use it. I will talk to
skhune@ and oshima@ about whether something already exists or if we need to add
it.

[mukesh agrawal, 2014/11/14 02:14:54]

I take it the idea is that components shouldn't depend on Chrome?

Based on that, I've removed the include of chrome/browser/profiles/profile.h,
and updated this factory's interface accordingly.

+  return new WifiCredentialSyncableService(context);
+}
+
+}  // namespace wifi_sync