Migrate invalidator client IDs out of sync

sync/notifier/sync_invalidation_listener.cc

Index: sync/notifier/sync_invalidation_listener.cc
diff --git a/sync/notifier/sync_invalidation_listener.cc b/sync/notifier/sync_invalidation_listener.cc
index e84bc3893b20c633e93c092c4a6e0c6071f9380a..4e57bb85ed5a2096072ab572573d4d7cf01e431b 100644
--- a/sync/notifier/sync_invalidation_listener.cc
+++ b/sync/notifier/sync_invalidation_listener.cc
@@ -95,6 +95,16 @@ void SyncInvalidationListener::Start(
 
   registration_manager_.reset(
       new RegistrationManager(invalidation_client_.get()));
+
+  // TODO(rlarocque): This call exists as part of an effort to move the
+  // invalidator's ID out of sync.  It writes the provided (sync-managed) ID to
+  // storage that lives on the UI thread.  Once this has been in place for a
+  // milestone or two, we can remove it and start looking for invalidator client
+  // IDs exclusively in the InvalidationStateTracker.  See crbug.com/124142.
+  invalidation_state_tracker_.Call(
+      FROM_HERE,
+      &InvalidationStateTracker::SetInvalidatorClientId,
+      client_id);
 }
 
 void SyncInvalidationListener::UpdateCredentials(