1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
// Copyright (c) 2012 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
#ifndef SYNC_ENGINE_SYNCER_TYPES_H_
#define SYNC_ENGINE_SYNCER_TYPES_H_
// The intent of this is to keep all shared data types and enums for the syncer
// in a single place without having dependencies between other files.
namespace syncer {
enum UpdateAttemptResponse {
// Update was applied or safely ignored.
SUCCESS,
// The conditions described by the following enum values are not mutually
// exclusive. The list has been ordered according to priority in the case of
// overlap, with highest priority first.
//
// For example, in the case where an item had both the IS_UNSYCNED and
// IS_UNAPPLIED_UPDATE flags set (CONFLICT_SIMPLE), and a SERVER_PARENT_ID
// that, if applied, would cause a directory loop (CONFLICT_HIERARCHY), and
// specifics that we can't decrypt right now (CONFLICT_ENCRYPTION), the
// UpdateApplicator would return CONFLICT_ENCRYPTION when attempting to
// process the item.
//
// We do not attempt to resolve CONFLICT_HIERARCHY or CONFLICT_ENCRYPTION
// items. We will leave these updates unapplied and wait for the server
// to send us newer updates that will resolve the conflict.
// We were unable to decrypt/encrypt this server data. As such, we can't make
// forward progress on this node, but because the passphrase may not arrive
// until later we don't want to get the syncer stuck. See UpdateApplicator
// for how this is handled.
CONFLICT_ENCRYPTION,
// These are some updates that, if applied, would violate the tree's
// invariants. Examples of this include the server adding children to locally
// deleted directories and directory moves that would create loops.
CONFLICT_HIERARCHY,
// This indicates that item was modified both remotely (IS_UNAPPLIED_UPDATE)
// and locally (IS_UNSYNCED). We use the ConflictResolver to decide which of
// the changes should take priority, or if we can possibly merge the data.
CONFLICT_SIMPLE
};
enum ServerUpdateProcessingResult {
// Success. Update applied and stored in SERVER_* fields or dropped if
// irrelevant.
SUCCESS_PROCESSED,
// Success. Update details stored in SERVER_* fields, but wasn't applied.
SUCCESS_STORED,
// Update is illegally inconsistent with earlier updates. e.g. A bookmark
// becoming a folder.
FAILED_INCONSISTENT,
// Update is illegal when considered alone. e.g. broken UTF-8 in the name.
FAILED_CORRUPT,
// Only used by VerifyUpdate. Indicates that an update is valid. As
// VerifyUpdate cannot return SUCCESS_STORED, we reuse the value.
SUCCESS_VALID = SUCCESS_STORED
};
// Different results from the verify phase will yield different methods of
// processing in the ProcessUpdates phase. The SKIP result means the entry
// doesn't go to the ProcessUpdates phase.
enum VerifyResult {
VERIFY_FAIL,
VERIFY_SUCCESS,
VERIFY_UNDELETE,
VERIFY_SKIP,
VERIFY_UNDECIDED
};
enum VerifyCommitResult {
VERIFY_UNSYNCABLE,
VERIFY_OK,
};
} // namespace syncer
#endif // SYNC_ENGINE_SYNCER_TYPES_H_
|
