diff options
| author | tim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-08 19:07:36 +0000 |
|---|---|---|
| committer | tim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-08 19:07:36 +0000 |
| commit | 1ce52aae084f6a0201c64141e35772fc70bab1f0 (patch) | |
| tree | f1d3ee1f356df34f5746f4659c05b0de5438a808 /chrome/browser/sync/engine/syncapi.h | |
| parent | af3711395a43fc47aa5882148edc93d9674dcdf1 (diff) | |
| download | chromium_src-1ce52aae084f6a0201c64141e35772fc70bab1f0.zip chromium_src-1ce52aae084f6a0201c64141e35772fc70bab1f0.tar.gz chromium_src-1ce52aae084f6a0201c64141e35772fc70bab1f0.tar.bz2 | |
Implements the backend for clearing data from the server
BUG=54280
TEST=accessible only via unit test checked in this CL
Original patch by raz@chromium.org
Original review: http://codereview.chromium.org/3293007
Review URL: http://codereview.chromium.org/3310018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58859 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/sync/engine/syncapi.h')
| -rw-r--r-- | chrome/browser/sync/engine/syncapi.h | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/chrome/browser/sync/engine/syncapi.h b/chrome/browser/sync/engine/syncapi.h index e4e8510..c49fc67 100644 --- a/chrome/browser/sync/engine/syncapi.h +++ b/chrome/browser/sync/engine/syncapi.h @@ -700,6 +700,11 @@ class SyncManager { // global stop syncing operation has wiped the store. virtual void OnStopSyncingPermanently() = 0; + // After a request to clear server data, these callbacks are invoked to + // indicate success or failure + virtual void OnClearServerDataSucceeded() = 0; + virtual void OnClearServerDataFailed() = 0; + private: DISALLOW_COPY_AND_ASSIGN(Observer); }; @@ -814,6 +819,9 @@ class SyncManager { // to run at the next available opportunity. void RequestNudge(); + // Request a clearing of all data on the server + void RequestClearServerData(); + // Adds a listener to be notified of sync events. // NOTE: It is OK (in fact, it's probably a good idea) to call this before // having received OnInitializationCompleted. |