/external/chromium_org/sync/test/engine/ |
test_directory_setter_upper.cc | 63 directory()->SaveChanges(); 65 directory()->SaveChanges();
|
/external/chromium_org/sync/internal_api/test/ |
test_user_share.cc | 44 if (!user_share_->directory->SaveChanges())
|
fake_sync_manager.cc | 208 void FakeSyncManager::SaveChanges() {
|
/external/chromium_org/sync/syncable/ |
syncable_unittest.cc | 212 dir.SaveChanges(); 281 dir.SaveChanges(); 309 dir.SaveChanges(); 356 dir.SaveChanges(); 416 dir.SaveChanges(); 466 dir_->SaveChanges(); 618 // Fake SaveChanges() and make sure we got what we expected. 651 // Fake SaveChanges() and make sure we got what we expected. 681 dir_->SaveChanges(); 702 dir_->SaveChanges(); [all...] |
directory_backing_store.h | 68 // calls SaveChanges *must* be the thread that owns/destroys |this|. 69 virtual bool SaveChanges(const Directory::SaveChangesSnapshot& snapshot);
|
directory.h | 134 // When the Directory is told to SaveChanges, a SaveChangesSnapshot is 295 // SaveChanges works by taking a consistent snapshot of the current Directory 300 // internal locking to enforce SaveChanges operations are mutually exclusive. 303 bool SaveChanges(); 312 // Get GetUnsyncedMetaHandles should only be called after SaveChanges and 448 // them in here so that SaveChanges can persist their permanent deletion. 457 // database on SaveChanges. 464 // It doesn't make sense for two threads to run SaveChanges at the same 494 // See SaveChanges() for more information. 498 // successfully deleted on disk as a result of the SaveChanges that processe [all...] |
directory.cc | 179 if (!SaveChanges()) 515 bool Directory::SaveChanges() { 523 success = store_->SaveChanges(snapshot); 755 // that SaveChanges will at least try again later. [all...] |
directory_backing_store.cc | 202 bool DirectoryBackingStore::SaveChanges( [all...] |
/external/chromium/chrome/browser/sync/syncable/ |
syncable_unittest.cc | 181 dir.SaveChanges(); 204 dir.SaveChanges(); 241 dir.SaveChanges(); 293 dir.SaveChanges(); 296 // A Directory whose backing store always fails SaveChanges by returning false. 304 virtual bool SaveChanges(const Directory::SaveChangesSnapshot& snapshot) { 335 dir_->SaveChanges(); 347 dir_->SaveChanges(); 467 // Fake SaveChanges() and make sure we got what we expected. 500 // Fake SaveChanges() and make sure we got what we expected [all...] |
directory_backing_store.h | 47 // 2. Requires that SaveChanges *only* be called from a single thread, and that 52 // SaveChanges is called a new sqlite3 handle is created, and it will get closed 73 // calls SaveChanges *must* be the thread that owns/destroys |this|. 74 virtual bool SaveChanges(const Directory::SaveChangesSnapshot& snapshot); 142 // Lazy creation of save_dbhandle_ for use by SaveChanges code path. 183 // for saving changes periodically via SaveChanges, respectively. 186 // or SyncCore threads, but SaveChanges is always called by the latter. We
|
directory_manager.cc | 117 managed_directory_->SaveChanges();
|
directory_backing_store.cc | 32 // is calling SaveChanges. In the worst case scenario, the user can put his 350 bool DirectoryBackingStore::SaveChanges( [all...] |
syncable.h | 730 // When the Directory is told to SaveChanges, a SaveChangesSnapshot is 857 // SaveChanges works by taking a consistent snapshot of the current Directory 862 // internal locking to enforce SaveChanges operations are mutually exclusive. 865 bool SaveChanges(); 870 // Get GetUnsyncedMetaHandles should only be called after SaveChanges and 919 // See SaveChanges() for more information. 923 // successfully deleted on disk as a result of the SaveChanges that processed 924 // |snapshot|. See SaveChanges() for more information. 927 // Rolls back dirty bits in the event that the SaveChanges that [all...] |
syncable.cc | 625 bool Directory::SaveChanges() { 634 success = store_->SaveChanges(snapshot); 741 // that SaveChanges will at least try again later. [all...] |
/external/chromium_org/sync/internal_api/public/ |
sync_manager.h | 395 virtual void SaveChanges() = 0; 397 // Issue a final SaveChanges, and close sqlite handles.
|
/external/chromium_org/sync/internal_api/public/test/ |
fake_sync_manager.h | 116 virtual void SaveChanges() OVERRIDE;
|
/external/chromium_org/chrome/browser/sync/glue/ |
sync_backend_host_core.cc | 158 // SaveChanges. 613 this, &SyncBackendHostCore::SaveChanges); 616 void SyncBackendHostCore::SaveChanges() { 618 sync_manager_->SaveChanges();
|
sync_backend_host_core.h | 230 // This must be called from the thread on which SaveChanges is intended to 239 void SaveChanges(); 258 // The timer used to periodically call SaveChanges.
|
/external/chromium_org/sync/internal_api/ |
sync_manager_impl.h | 108 virtual void SaveChanges() OVERRIDE;
|
sync_manager_impl.cc | 665 directory()->SaveChanges(); [all...] |
/external/chromium/chrome/browser/sync/glue/ |
sync_backend_host.h | 370 // SaveChanges, close sqlite handles, and halt the syncer thread (which 435 // This must be called from the thread on which SaveChanges is intended to 445 void SaveChanges(); 500 // The timer used to periodically call SaveChanges.
|
sync_backend_host.cc | [all...] |
/external/chromium/chrome/browser/sync/engine/ |
syncapi.cc | [all...] |
syncapi.h | [all...] |
/external/chromium_org/sync/engine/ |
syncer_unittest.cc | [all...] |