OLD | NEW |
1 // Copyright 2014 The Chromium Authors. All rights reserved. | 1 // Copyright 2014 The Chromium Authors. All rights reserved. |
2 // Use of this source code is governed by a BSD-style license that can be | 2 // Use of this source code is governed by a BSD-style license that can be |
3 // found in the LICENSE file. | 3 // found in the LICENSE file. |
4 | 4 |
5 This framework was once used to implement an asynchronous request/reply | 5 This framework was once used to implement an asynchronous request/reply |
6 protocol between the chrome://sync-internals page and the sync backend thread. | 6 protocol between the chrome://sync-internals page and the sync backend thread. |
7 Much of it has been removed in favor of an ad-hoc system that allows us to | 7 Much of it has been removed in favor of an ad-hoc system that allows us to |
8 offer better safety guarantees, and to dispatch requests to different threads. | 8 offer better safety guarantees, and to dispatch requests to different threads. |
9 | 9 |
10 All that remains are some WeakHandles that allow us to send JsEvents from the | 10 All that remains are some WeakHandles that allow us to send JsEvents from the |
11 sync backend to about:sync. The SyncInternalsUI implements JsEventHandler in | 11 sync backend to about:sync. The SyncInternalsUI implements JsEventHandler in |
12 order to receive these events. The SyncManager implements JsBackend in order | 12 order to receive these events. The SyncManager implements JsBackend in order |
13 to send them. The SyncJsController acts as an intermediary between them. | 13 to send them. The SyncJsController acts as an intermediary between them. |
14 | 14 |
15 The old framework may still be useful to someone. Feel free to retrieve it | 15 The old framework may still be useful to someone. Feel free to retrieve it |
16 from SVN history if you feel you can make use of it. | 16 from SVN history if you feel you can make use of it. |
OLD | NEW |