summaryrefslogtreecommitdiffstats
path: root/sync/sync.gyp
diff options
context:
space:
mode:
authorrlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-05-26 00:06:47 +0000
committerrlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-05-26 00:06:47 +0000
commitce0f41696951562391ad3d1bf180c2ae08db66fb (patch)
treea502e5d771252e26df5f51477eb477696a2dc7f7 /sync/sync.gyp
parent085e92da549d6e20df4e023687aad2c23e05aea2 (diff)
downloadchromium_src-ce0f41696951562391ad3d1bf180c2ae08db66fb.zip
chromium_src-ce0f41696951562391ad3d1bf180c2ae08db66fb.tar.gz
chromium_src-ce0f41696951562391ad3d1bf180c2ae08db66fb.tar.bz2
sync: Loop committing items without downloading updates
Since its inception sync has required all commits to be preceded by a GetUpdates request. This was done to try to ensure we detect and resolve conflicts on the client, rather than having two conflicting commits collide at the server. It could never work perfectly, but it was likely to work in most cases and the server would bounce the commit if it didn't. Now we have a new server that doesn't always give us the latest version of a node when we ask for it, especially when the request was not solicited by the server (ie. not triggered by notification). The update before commit is now much less likely to detect conflicts. Even worse, the useless update requests can be surprisingly expensive in certain scenarios. This change allows us to avoid fetching updates between 'batches' of commits. This should improve performance in the case where we have lots of items to commit (ie. first time sync) and reduce load on the server. This CL has some far-reaching effects. This is in part because I decided to refactor the commit code, but major changes would have been required with or without the refactor. Highlights include: - The commit-related SyncerCommands are now paramaterized with local variables, allowing us to remove many members from the SyncSession classes. - Several syncer states have been collapsed into one COMMIT state which redirects to the new BuildAndPostCommits() function. - The PostCommitMessageCommand had been reduced to one line, which has now been inlined into the BuildAndPostCommits() function. - The unsynced_handles counter has been removed for now. Following this change, it would have always been zero unless an error was encountered during the commit. The functions that reference it expect different behaviour and would have been broken by this change. - The code to put extensions activity data back into the ExtensionsActivityMonitor in case of failure has been moved around to avoid double-counting if we have to post many commit messages. - A CONFLICT response from the server is now treated as a transient error. If we had continued to treat it as a success we might risk going into an infinite loop. See comment in code for details. - The "purposeless anachronism" conflicting_new_folder_ids_ has been removed. Review URL: https://chromiumcodereview.appspot.com/10210009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139159 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync/sync.gyp')
-rw-r--r--sync/sync.gyp4
1 files changed, 2 insertions, 2 deletions
diff --git a/sync/sync.gyp b/sync/sync.gyp
index f10d249..8bb5c2c 100644
--- a/sync/sync.gyp
+++ b/sync/sync.gyp
@@ -41,6 +41,8 @@
'engine/cleanup_disabled_types_command.h',
'engine/clear_data_command.cc',
'engine/clear_data_command.h',
+ 'engine/commit.cc',
+ 'engine/commit.h',
'engine/conflict_resolver.cc',
'engine/conflict_resolver.h',
'engine/download_updates_command.cc',
@@ -63,8 +65,6 @@
'engine/nudge_source.h',
'engine/polling_constants.cc',
'engine/polling_constants.h',
- 'engine/post_commit_message_command.cc',
- 'engine/post_commit_message_command.h',
'engine/process_commit_response_command.cc',
'engine/process_commit_response_command.h',
'engine/process_updates_command.cc',