• Home
  • History
  • Annotate
  • only in /external/chromium_org/sync/internal_api/

..12-Mar-20154 KiB

attachments/12-Mar-20154 KiB

base_node.cc12-Mar-201510.4 KiB

base_transaction.cc12-Mar-20151 KiB

change_record.cc12-Mar-20151.8 KiB

change_reorder_buffer.cc12-Mar-20157.3 KiB

change_reorder_buffer.h12-Mar-20153.2 KiB

debug_info_event_listener.cc12-Mar-20159.4 KiB

debug_info_event_listener.h12-Mar-20154.6 KiB

debug_info_event_listener_unittest.cc12-Mar-20152.3 KiB

delete_journal.cc12-Mar-20152.2 KiB


events/12-Mar-20154 KiB

http_bridge.cc12-Mar-201514.8 KiB

http_bridge_network_resources.cc12-Mar-20151.1 KiB

http_bridge_unittest.cc12-Mar-201519.2 KiB

internal_components_factory_impl.cc12-Mar-20153 KiB

js_mutation_event_observer.cc12-Mar-20153.4 KiB

js_mutation_event_observer.h12-Mar-20152.1 KiB

js_mutation_event_observer_unittest.cc12-Mar-20153.7 KiB

js_sync_encryption_handler_observer.cc12-Mar-20154 KiB

js_sync_encryption_handler_observer.h12-Mar-20152.1 KiB

js_sync_encryption_handler_observer_unittest.cc12-Mar-20156.1 KiB

js_sync_manager_observer.cc12-Mar-20153 KiB

js_sync_manager_observer.h12-Mar-20152 KiB

js_sync_manager_observer_unittest.cc12-Mar-20153.7 KiB

protocol_event_buffer.cc12-Mar-20151 KiB

protocol_event_buffer.h12-Mar-20151.1 KiB

protocol_event_buffer_unittest.cc12-Mar-20152.4 KiB

public/12-Mar-20154 KiB

read_node.cc12-Mar-20153.9 KiB

read_transaction.cc12-Mar-20151.8 KiB

README12-Mar-20152 KiB

sync_backup_manager.cc12-Mar-20154.7 KiB

sync_backup_manager.h12-Mar-20152.3 KiB

sync_backup_manager_unittest.cc12-Mar-20156.6 KiB



sync_context_proxy_impl.cc12-Mar-20151.9 KiB

sync_context_proxy_impl.h12-Mar-20152.2 KiB

sync_context_proxy_impl_unittest.cc12-Mar-20153.4 KiB

sync_db_util.cc12-Mar-20151.2 KiB

sync_encryption_handler_impl.cc12-Mar-201567.8 KiB

sync_encryption_handler_impl.h12-Mar-201514 KiB

sync_encryption_handler_impl_unittest.cc12-Mar-201596 KiB

sync_manager_factory.cc12-Mar-20151 KiB

sync_manager_impl.cc12-Mar-201537.6 KiB

sync_manager_impl.h12-Mar-201514.4 KiB

sync_manager_impl_unittest.cc12-Mar-2015123 KiB

sync_rollback_manager.cc12-Mar-20154 KiB

sync_rollback_manager.h12-Mar-20151.3 KiB

sync_rollback_manager_base.cc12-Mar-201510.4 KiB

sync_rollback_manager_base.h12-Mar-20155.8 KiB

sync_rollback_manager_base_unittest.cc12-Mar-20152.8 KiB

sync_rollback_manager_unittest.cc12-Mar-20159.3 KiB

syncapi_internal.cc12-Mar-20154 KiB

syncapi_internal.h12-Mar-20151.5 KiB

syncapi_server_connection_manager.cc12-Mar-20153.5 KiB

syncapi_server_connection_manager.h12-Mar-20152.8 KiB

syncapi_server_connection_manager_unittest.cc12-Mar-20154.3 KiB

test/12-Mar-20154 KiB


write_node.cc12-Mar-201518.6 KiB

write_transaction.cc12-Mar-20153.8 KiB


1This file defines the "sync API", an interface to the syncer
2backend that exposes (1) the core functionality of maintaining a consistent
3local snapshot of a hierarchical object set; (2) a means to transactionally
4access and modify those objects; (3) a means to control client/server
5synchronization tasks, namely: pushing local object modifications to a
6server, pulling nonlocal object modifications from a server to this client,
7and resolving conflicts that may arise between the two; and (4) an
8abstraction of some external functionality that is to be provided by the
9host environment.
11This interface is used as the entry point into the syncer backend
12when the backend is compiled as a library and embedded in another
13application.  A goal for this interface layer is to depend on very few
14external types, so that an application can use the sync backend
15without introducing a dependency on specific types.  A non-goal is to
16have binary compatibility across versions or compilers; this allows the
17interface to use C++ classes.  An application wishing to use the sync API
18should ideally compile the syncer backend and this API as part of the
19application's own build, to avoid e.g. mismatches in calling convention,
20structure padding, or name mangling that could arise if there were a
21compiler mismatch.
23The schema of the objects in the sync domain is based on the model, which
24is essentially a hierarchy of items and folders similar to a filesystem,
25but with a few important differences.  The sync API contains fields
26such as URL to easily allow the embedding application to store web
27browser bookmarks.  Also, the sync API allows duplicate titles in a parent.
28Consequently, it does not support looking up an object by title
29and parent, since such a lookup is not uniquely determined.  Lastly,
30unlike a filesystem model, objects in the Sync API model have a strict
31ordering within a parent; the position is manipulable by callers, and
32children of a node can be enumerated in the order of their position.