summaryrefslogtreecommitdiffstats
path: root/printing
diff options
context:
space:
mode:
authornick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-04-23 01:53:16 +0000
committernick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-04-23 01:53:16 +0000
commit4724e4139b6e7c1d48acee1b788ab0c1598a9406 (patch)
tree7229c06fbb31e541fa74ff05d4468addf637d5c1 /printing
parentea892b7054057ed3de9aab2a2e6f1f25f701c3da (diff)
downloadchromium_src-4724e4139b6e7c1d48acee1b788ab0c1598a9406.zip
chromium_src-4724e4139b6e7c1d48acee1b788ab0c1598a9406.tar.gz
chromium_src-4724e4139b6e7c1d48acee1b788ab0c1598a9406.tar.bz2
Python sync server support for MIGRATION_DONE errors.
This allows a test or a user to inject MIGRATION_DONE errors on arbitrary datatypes. Clients that encounter such an error will fail until they re-sync the affected datatypes. For GetUpdates, the error is determined by embedding the migration version (an increasing integer value) in the progress_marker's token. Old version numbers ==> ERROR. For Commit, the error is determined by embedding the migration number in the ID of every object. Doing so also guarantees that the client has actually redownloaded -- IDs are invalidated across a migration boundary. Bonus fixes: greatly enhanced logging info, embed the datatype in the ID. BUG=79247 TEST=sync_integration_tests Review URL: http://codereview.chromium.org/6870029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@82766 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'printing')
0 files changed, 0 insertions, 0 deletions