components/sync/core_impl/README - Issue 2130453004: [Sync] Move //sync to //components/sync.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: components/sync/core_impl/README

Issue 2130453004: [Sync] Move //sync to //components/sync. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Rebase. Created 4 years, 4 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « components/sync/core_impl/DEPS ('k') | components/sync/core_impl/attachments/DEPS » ('j') | no next file with comments »

OLD	NEW
1 This file defines the "sync API", an interface to the syncer	1 This file defines the "sync API", an interface to the syncer

2 backend that exposes (1) the core functionality of maintaining a consistent	2 backend that exposes (1) the core functionality of maintaining a consistent

3 local snapshot of a hierarchical object set; (2) a means to transactionally	3 local snapshot of a hierarchical object set; (2) a means to transactionally

4 access and modify those objects; (3) a means to control client/server	4 access and modify those objects; (3) a means to control client/server

5 synchronization tasks, namely: pushing local object modifications to a	5 synchronization tasks, namely: pushing local object modifications to a

6 server, pulling nonlocal object modifications from a server to this client,	6 server, pulling nonlocal object modifications from a server to this client,

7 and resolving conflicts that may arise between the two; and (4) an	7 and resolving conflicts that may arise between the two; and (4) an

8 abstraction of some external functionality that is to be provided by the	8 abstraction of some external functionality that is to be provided by the

9 host environment.	9 host environment.

10	10

(...skipping 12 matching lines...) Expand all Loading...
23 The schema of the objects in the sync domain is based on the model, which	23 The schema of the objects in the sync domain is based on the model, which

24 is essentially a hierarchy of items and folders similar to a filesystem,	24 is essentially a hierarchy of items and folders similar to a filesystem,

25 but with a few important differences. The sync API contains fields	25 but with a few important differences. The sync API contains fields

26 such as URL to easily allow the embedding application to store web	26 such as URL to easily allow the embedding application to store web

27 browser bookmarks. Also, the sync API allows duplicate titles in a parent.	27 browser bookmarks. Also, the sync API allows duplicate titles in a parent.

28 Consequently, it does not support looking up an object by title	28 Consequently, it does not support looking up an object by title

29 and parent, since such a lookup is not uniquely determined. Lastly,	29 and parent, since such a lookup is not uniquely determined. Lastly,

30 unlike a filesystem model, objects in the Sync API model have a strict	30 unlike a filesystem model, objects in the Sync API model have a strict

31 ordering within a parent; the position is manipulable by callers, and	31 ordering within a parent; the position is manipulable by callers, and

32 children of a node can be enumerated in the order of their position.	32 children of a node can be enumerated in the order of their position.

OLD	NEW