OLD | NEW |
1 Overview of chrome://sync-internals | 1 Overview of chrome://sync-internals |
2 ----------------------------------- | 2 ----------------------------------- |
3 | 3 |
4 This note explains how chrome://sync-internals (also known as | 4 This note explains how chrome://sync-internals (also known as |
5 about:sync) interacts with the sync service/backend. | 5 about:sync) interacts with the sync service/backend. |
6 | 6 |
7 Basically, chrome://sync-internals sends messages to the sync backend | 7 Basically, chrome://sync-internals sends messages to the sync backend |
8 and the sync backend sends the reply asynchronously. The sync backend | 8 and the sync backend sends the reply asynchronously. The sync backend |
9 also asynchronously raises events which chrome://sync-internals listen | 9 also asynchronously raises events which chrome://sync-internals listen |
10 to. | 10 to. |
(...skipping 28 matching lines...) Expand all Loading... |
39 | 39 |
40 - SyncInternalsUI (implements JsEventHandler, JsReplyHandler) | 40 - SyncInternalsUI (implements JsEventHandler, JsReplyHandler) |
41 - SyncJsController (implements JsController, JsEventHandler) | 41 - SyncJsController (implements JsController, JsEventHandler) |
42 | 42 |
43 The following objects live on the sync thread: | 43 The following objects live on the sync thread: |
44 | 44 |
45 - SyncManager::SyncInternal (implements JsBackend) | 45 - SyncManager::SyncInternal (implements JsBackend) |
46 | 46 |
47 Of course, none of these objects need to know where the other objects | 47 Of course, none of these objects need to know where the other objects |
48 live, since they interact via WeakHandles. | 48 live, since they interact via WeakHandles. |
OLD | NEW |