Use OAuth2 token for sync

sync/internal_api/sync_manager_impl.cc

Index: sync/internal_api/sync_manager_impl.cc
diff --git a/sync/internal_api/sync_manager_impl.cc b/sync/internal_api/sync_manager_impl.cc
index aae5d418543d163dea1cac4019d80a3c2658a571..e8dc391edab514f23d10e24cc7261936c1372873 100644
--- a/sync/internal_api/sync_manager_impl.cc
+++ b/sync/internal_api/sync_manager_impl.cc
@@ -597,10 +597,14 @@ void SyncManagerImpl::UpdateCredentials(const SyncCredentials& credentials) {
   DCHECK(!credentials.email.empty());
   DCHECK(!credentials.sync_token.empty());
 
-  observing_network_connectivity_changes_ = true;
   if (!connection_manager_->set_auth_token(credentials.sync_token))
     return;  // Auth token is known to be invalid, so exit early.
 
+  if (connection_manager_->server_status() == HttpResponse::SYNC_AUTH_ERROR)
+    connection_manager_->SetServerStatus(HttpResponse::TOKEN_REFRESHED);
+

[Andrew T Wilson (Slow), 2013/05/24 14:10:15]

Hmm. I'm not sure why it's safe to move
"observing_network_connectivity_changes_=true" down here after the early exit
above.

I'm also not sure why we need this TOKEN_REFRESHED state - from the standpoint
of the SyncManager why didn't the old implementation work?

[pavely, 2013/05/30 07:42:12]

if(set_auth_token) condition means "New credentials are still no good for
talking to server. I won't even try". Presumably connecting to server when
connection is restored will not succeed, thus moving
observing_network_connectivity_changes_=true.

TOKEN_REFRESHED was used in more places in earlier version of this change. I
didn't realize i don't need it anymore.

I'll revert both changes.

+  observing_network_connectivity_changes_ = true;
+
   invalidator_->UpdateCredentials(credentials.email, credentials.sync_token);
   scheduler_->OnCredentialsUpdated();
 }