• Home
  • History
  • Annotate
  • only in /external/chromium/chrome/browser/sync/
NameDateSize

..03-Jan-201420 KiB

abstract_profile_sync_service_test.cc03-Jan-20144 KiB

abstract_profile_sync_service_test.h03-Jan-20141.9 KiB

backend_migrator.cc03-Jan-20146.2 KiB

backend_migrator.h03-Jan-20142.3 KiB

backend_migrator_unittest.cc03-Jan-20149.9 KiB

DEPS03-Jan-2014108

engine/03-Jan-20144 KiB

glue/03-Jan-201412 KiB

js_arg_list.cc03-Jan-20141.5 KiB

js_arg_list.h03-Jan-20141.4 KiB

js_arg_list_unittest.cc03-Jan-20141.6 KiB

js_backend.h03-Jan-20141.2 KiB

js_event_handler.h03-Jan-2014709

js_event_handler_list.cc03-Jan-20142.7 KiB

js_event_handler_list.h03-Jan-20142.3 KiB

js_event_handler_list_unittest.cc03-Jan-20144 KiB

js_event_router.h03-Jan-20141.1 KiB

js_frontend.h03-Jan-20141.2 KiB

js_sync_manager_observer.cc03-Jan-20144.5 KiB

js_sync_manager_observer.h03-Jan-20141.9 KiB

js_sync_manager_observer_unittest.cc03-Jan-20149.7 KiB

js_test_util.cc03-Jan-20141.9 KiB

js_test_util.h03-Jan-20142.3 KiB

notifier/03-Jan-20144 KiB

PRESUBMIT.py03-Jan-2014479

profile_sync_factory.h03-Jan-20145.6 KiB

profile_sync_factory_impl.cc03-Jan-201413.5 KiB

profile_sync_factory_impl.h03-Jan-20142.9 KiB

profile_sync_factory_impl_unittest.cc03-Jan-20145.2 KiB

profile_sync_factory_mock.cc03-Jan-20141.2 KiB

profile_sync_factory_mock.h03-Jan-20143.6 KiB

profile_sync_service.cc03-Jan-201443.9 KiB

profile_sync_service.h03-Jan-201425.8 KiB

profile_sync_service_autofill_unittest.cc03-Jan-201443.1 KiB

profile_sync_service_bookmark_unittest.cc03-Jan-201448 KiB

profile_sync_service_harness.cc03-Jan-201422 KiB

profile_sync_service_harness.h03-Jan-20148.4 KiB

profile_sync_service_mock.cc03-Jan-2014481

profile_sync_service_mock.h03-Jan-20142.7 KiB

profile_sync_service_observer.h03-Jan-20141,006

profile_sync_service_password_unittest.cc03-Jan-201423.5 KiB

profile_sync_service_preference_unittest.cc03-Jan-201419 KiB

profile_sync_service_session_unittest.cc03-Jan-201416.9 KiB

profile_sync_service_startup_unittest.cc03-Jan-201410.1 KiB

profile_sync_service_typed_url_unittest.cc03-Jan-201421.8 KiB

profile_sync_service_unittest.cc03-Jan-201413.7 KiB

profile_sync_test_util.cc03-Jan-20142.5 KiB

profile_sync_test_util.h03-Jan-20142.5 KiB

protocol/03-Jan-20144 KiB

README.js03-Jan-20142.4 KiB

resources/03-Jan-20144 KiB

sessions/03-Jan-20144 KiB

signin_manager.cc03-Jan-20145.8 KiB

signin_manager.h03-Jan-20143.3 KiB

signin_manager_unittest.cc03-Jan-20145.7 KiB

sync_setup_flow.cc03-Jan-201415.2 KiB

sync_setup_flow.h03-Jan-20146.3 KiB

sync_setup_flow_handler.h03-Jan-20141.2 KiB

sync_setup_wizard.cc03-Jan-20142.6 KiB

sync_setup_wizard.h03-Jan-20143.5 KiB

sync_setup_wizard_unittest.cc03-Jan-201419.8 KiB

sync_ui_util.cc03-Jan-201417.6 KiB

sync_ui_util.h03-Jan-20142.8 KiB

sync_ui_util_mac.h03-Jan-2014922

sync_ui_util_mac.mm03-Jan-20142.4 KiB

sync_ui_util_mac_unittest.mm03-Jan-20143.9 KiB

sync_ui_util_unittest.cc03-Jan-20141.5 KiB

syncable/03-Jan-20144 KiB

test_profile_sync_service.cc03-Jan-20148.8 KiB

test_profile_sync_service.h03-Jan-20144.6 KiB

tools/03-Jan-20144 KiB

unrecoverable_error_handler.h03-Jan-2014972

util/03-Jan-20144 KiB

README.js

1Overview of chrome://sync-internals
2-----------------------------------
3
4This note explains how chrome://sync-internals (also known as
5about:sync) interacts with the sync service/backend.
6
7Basically, chrome://sync-internals sends asynchronous messages to the
8sync backend and the sync backend asynchronously raises events to
9chrome://sync-internals, either when replying to messages or when
10something interesting happens.
11
12Both messages and events have a name and a list of arguments, the
13latter of which is represented by a JsArgList (js_arg_list.h) object,
14which is basically a wrapper around an immutable ListValue.
15
16TODO(akalin): Move all the js_* files into a js/ subdirectory.
17
18Message/event flow
19------------------
20
21chrome://sync-internals is represented by SyncInternalsUI
22(chrome/browser/web_ui/sync_internals_ui.h).  SyncInternalsUI
23interacts with the sync service via a JsFrontend (js_frontend.h)
24object, which has a ProcessMessage() method.  The JsFrontend can
25handle some messages itself, but it can also delegate the rest to a
26JsBackend instance (js_backend.h), which also has a ProcessMessage()
27method.  A JsBackend can in turn handle some messages itself and
28delegate to other JsBackend instances.
29
30Essentially, there is a tree with a JsFrontend as the root and
31JsBackend as non-root internal nodes and leaf nodes (although
32currently, the tree is more like a simple list).  The sets of messages
33handled by the JsBackends and the JsFrontend are disjoint, which means
34that at most one node handles a given message type.  Also, the
35JsBackends may live on different threads, but JsArgList is thread-safe
36so that's okay.
37
38SyncInternalsUI is a JsEventHandler (js_event_handler.h), which means
39that it has a HandleJsEvent() method, but JsBackends cannot easily
40access those objects.  Instead, each JsBackend keeps track of its
41parent router, which is a JsEventRouter object (js_event_router.h).
42Basically, a JsEventRouter is another JsBackend object or a JsFrontend
43object.  So an event travels up through the JsEventRouter until it
44reaches the JsFrontend, which knows about the existing JsEventHandlers
45(via AddHandler()/RemoveHandler()) and so can delegate to the right
46one.
47
48A diagram of the flow of a message and its reply:
49
50msg(args) -> F -> B -> B -> B
51             |    |    |
52        H <- R <- R <- R <- reply-event(args)
53
54F = JsFrontend, B = JsBackend, R = JsEventRouter, H = JsEventHandler
55
56Non-reply events are percolated up similarly.
57