diff options
| author | tim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-08-15 22:00:54 +0000 |
|---|---|---|
| committer | tim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-08-15 22:00:54 +0000 |
| commit | 92be5a41c4a56014723da338a53f5cbed515fe77 (patch) | |
| tree | 79caf856a5c116b52af1ae35932b604790af970a /google_apis/cup/OWNERS | |
| parent | ea79ba9670fc957f0acfe6e4e55bc27d0ed52606 (diff) | |
| download | chromium_src-92be5a41c4a56014723da338a53f5cbed515fe77.zip chromium_src-92be5a41c4a56014723da338a53f5cbed515fe77.tar.gz chromium_src-92be5a41c4a56014723da338a53f5cbed515fe77.tar.bz2 | |
Allow ProfileSyncService to initialize backend when access token is not available.
The problem is that when access token is not available ProfileSyncService
would initiate request to get access token but defer backend initialization
until that token arrives. When device has no network connectivity this
will take arbitrarily long time.
The fix is to remove chech for access token and let ProfileSyncService
initialize backend. Later when syncer initiates RPC to server
ServerConnectionManager::PostBufferToPath will notice that auth_token is
empty and trigger auth error which in turn initiate request for new access
token.
BUG=273096
R=tim@chromium.org
Review URL: https://codereview.chromium.org/23225002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217843 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'google_apis/cup/OWNERS')
0 files changed, 0 insertions, 0 deletions