Searched defs:SaveChanges (Results 1 - 5 of 5) sorted by relevance

/external/chromium/chrome/browser/sync/syncable/
H A Ddirectory_backing_store.cc32 // is calling SaveChanges. In the worst case scenario, the user can put his
350 bool DirectoryBackingStore::SaveChanges( function in class:syncable::DirectoryBackingStore
H A Dsyncable_unittest.cc181 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) { function in class:syncable::TestUnsaveableDirectory::UnsaveableBackingStore
335 dir_->SaveChanges();
347 dir_->SaveChanges();
467 // Fake SaveChanges() and make sure we got what we expected.
500 // Fake SaveChanges() an
[all...]
H A Dsyncable.cc625 bool Directory::SaveChanges() { function in class:syncable::Directory
634 success = store_->SaveChanges(snapshot);
741 // that SaveChanges will at least try again later.
/external/chromium/chrome/browser/sync/glue/
H A Dsync_backend_host.cc932 // Initialization is complete, so we can schedule recurring SaveChanges.
1069 this, &Core::SaveChanges); member in class:browser_sync::Core
1081 void SyncBackendHost::Core::SaveChanges() { function in class:browser_sync::SyncBackendHost::Core
1082 syncapi_->SaveChanges();
/external/chromium/chrome/browser/sync/engine/
H A Dsyncapi.cc1238 void SaveChanges();
2767 lookup->SaveChanges();
2790 void SyncManager::SaveChanges() { function in class:sync_api::SyncManager
2791 data_->SaveChanges();
2794 void SyncManager::SyncInternal::SaveChanges() { function in class:sync_api::SyncManager::SyncInternal
2797 DCHECK(false) << "ScopedDirLookup creation failed; Unable to SaveChanges";
2800 lookup->SaveChanges();

Completed in 979 milliseconds