Use InvalidationClient::Create() instead of creating an Impl directly.

chrome/browser/sync/notifier/server_notifier_thread.cc

Index: chrome/browser/sync/notifier/server_notifier_thread.cc
diff --git a/chrome/browser/sync/notifier/server_notifier_thread.cc b/chrome/browser/sync/notifier/server_notifier_thread.cc
index f52df43f2023f7124ac68eb880cd051df2e8c40f..81ac612e753a77608f3f2d57ced26a69e91d76ee 100644
--- a/chrome/browser/sync/notifier/server_notifier_thread.cc
+++ b/chrome/browser/sync/notifier/server_notifier_thread.cc
@@ -110,12 +110,12 @@ void ServerNotifierThread::StartInvalidationListener() {
   StopInvalidationListener();
   chrome_invalidation_client_.reset(new ChromeInvalidationClient());
 
-  // TODO(akalin): Make cache_guid() part of the app name.  If we do
+  // TODO(akalin): Make cache_guid() part of the client ID.  If we do
   // so and we somehow propagate it up to the server somehow, we can
   // make it so that we won't receive any notifications that were
   // generated from our own changes.
-  const std::string kAppName = "server_notifier_thread";
-  chrome_invalidation_client_->Start(kAppName, this, xmpp_client());
+  const std::string kClientId = "server_notifier_thread";
+  chrome_invalidation_client_->Start(kClientId, this, xmpp_client());
 }
 
 void ServerNotifierThread::RegisterTypesAndSignalSubscribed() {