| 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 093adb433b1159faa21aac0bd730f50f31937a05..a6377b8f275d66958c848d81f620b85c754a6e9c 100644
|
| --- a/chrome/browser/sync/notifier/server_notifier_thread.cc
|
| +++ b/chrome/browser/sync/notifier/server_notifier_thread.cc
|
| @@ -111,11 +111,11 @@ void ServerNotifierThread::StartInvalidationListener() {
|
| StopInvalidationListener();
|
| chrome_invalidation_client_.reset(new ChromeInvalidationClient());
|
|
|
| - // TODO(akalin): If we can figure out a unique per-session key that
|
| - // is preserved by the server, we can use that instead of kAppName.
|
| - // What this buys us is that we then won't receive any notifications
|
| - // that were generated by ourselves.
|
| - const std::string kAppName = "cc_sync_listen_notifications";
|
| + // TODO(akalin): Make cache_guid() part of the app name. 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());
|
| }
|
|
|
|
|