diff options
| author | skrul@chromium.org <skrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-06-29 20:37:06 +0000 |
|---|---|---|
| committer | skrul@chromium.org <skrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-06-29 20:37:06 +0000 |
| commit | 894f4a077ae70c658a285377c0f957c0259817d3 (patch) | |
| tree | 2934f824a8c3370326153f996e92f6a2fa61fb0e /third_party | |
| parent | ddd231eaa03153f6d04894cceb0b4480755e1277 (diff) | |
| download | chromium_src-894f4a077ae70c658a285377c0f957c0259817d3.zip chromium_src-894f4a077ae70c658a285377c0f957c0259817d3.tar.gz chromium_src-894f4a077ae70c658a285377c0f957c0259817d3.tar.bz2 | |
This change allows the syncer thread to be paused and resumed when the syncer thread has not yet been started or it has been started and is waiting for a connection.
From an API standpoint, the caller of SyncerThread::Pause and SyncerThread::Resume should not need to consider if the thread is already running. The channel responses (PAUSED and RESUMED) should be the same regardless. Furthermore, edge cases like "pause before thread is started and resume after thread is started" should be handled correctly.
This change is supposed to be fixing various offline startup problems we've been having and it includes a new integration test for this. However, it is not yet complete but we might need to check this is before it is ready.
TEST=unit
BUG=45814
Review URL: http://codereview.chromium.org/2814014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51158 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party')
0 files changed, 0 insertions, 0 deletions