diff options
| author | nick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-13 20:27:11 +0000 |
|---|---|---|
| committer | nick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-13 20:27:11 +0000 |
| commit | 55779e6a7c90f306405003383aabab7dc1d1abc6 (patch) | |
| tree | 2c9f50468b57329c06645ccc78e00d5b7cf5ced8 /o3d/samples/iframeit.html | |
| parent | a65aa987739a241f5581b94227e49245543080d0 (diff) | |
| download | chromium_src-55779e6a7c90f306405003383aabab7dc1d1abc6.zip chromium_src-55779e6a7c90f306405003383aabab7dc1d1abc6.tar.gz chromium_src-55779e6a7c90f306405003383aabab7dc1d1abc6.tar.bz2 | |
Fix handling of undeletion within the syncer.
Accomplished by:
(a) Plumbing the const CommitMessage into process_commit_response_command.cc, so that we can know the server state better (IS_DEL is no longer authoritative if !
which spilled over into a couple test expectations.
(b) Relaxing the enforced invariants that version==0 implied !ServerKnows, for items with client tags.
(c) Use ID renaming instead of delete/recreate to handle collisions on the unique tag.
(d) Upon deletion, version number goes to 0 so that the server knows to process the item as a recreate, if it gets undeleted. Previously, the server number would get synthesized on the client by incrementing the last known version number.
(e) Add unit tests for pretty much every ordering of delete/undelete I could come up with.
BUG=46769
TEST=unit tests; repeatedly uninstalled/installed extensions
Review URL: http://codereview.chromium.org/2844037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@52209 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'o3d/samples/iframeit.html')
0 files changed, 0 insertions, 0 deletions