Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(485)

Unified Diff: components/sync/api/metadata_change_list.h

Issue 2401223002: [Sync] Renaming sync/api* to sync/model*. (Closed)
Patch Set: Missed a comment in a DEPS file, and rebasing. Created 4 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « components/sync/api/metadata_batch.cc ('k') | components/sync/api/mock_model_type_store.h » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: components/sync/api/metadata_change_list.h
diff --git a/components/sync/api/metadata_change_list.h b/components/sync/api/metadata_change_list.h
deleted file mode 100644
index c20b7b9e6957a1a4a6fd32edd0d2a0d1a5ef7fbf..0000000000000000000000000000000000000000
--- a/components/sync/api/metadata_change_list.h
+++ /dev/null
@@ -1,50 +0,0 @@
-// Copyright 2015 The Chromium Authors. All rights reserved.
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
-
-#ifndef COMPONENTS_SYNC_API_METADATA_CHANGE_LIST_H_
-#define COMPONENTS_SYNC_API_METADATA_CHANGE_LIST_H_
-
-#include <string>
-
-namespace sync_pb {
-class EntityMetadata;
-class ModelTypeState;
-} // namespace sync_pb
-
-namespace syncer {
-
-// Interface used by the processor and service to communicate about metadata.
-// The purpose of the interface is to record changes to data type global and
-// per entity metadata for the purpose of propagating changes to the datatype
-// specific storage implementation.
-// The implementation of the interface is supposed to keep the record of all
-// updated / deleted metadata records and provide a mechanism to enumerate
-// them. If there are multiple UpdateMetadata / ClearMetadata calls made for the
-// same metadata record the last one is supposed to win.
-class MetadataChangeList {
- public:
- MetadataChangeList() {}
- virtual ~MetadataChangeList() {}
-
- // Requests ModelTypeState to be updated in the storage.
- virtual void UpdateModelTypeState(
- const sync_pb::ModelTypeState& model_type_state) = 0;
-
- // Requests ModelTypeState to be cleared from the storage.
- virtual void ClearModelTypeState() = 0;
-
- // Requests metadata entry to be updated in the storage.
- // Please note that the update might contain a deleted entry if
- // metadata.is_deleted() is true (as opposed to clearing the entry from the
- // storage completely by calling the Clear method).
- virtual void UpdateMetadata(const std::string& storage_key,
- const sync_pb::EntityMetadata& metadata) = 0;
-
- // Requests metadata entry to be cleared from the storage.
- virtual void ClearMetadata(const std::string& storage_key) = 0;
-};
-
-} // namespace syncer
-
-#endif // COMPONENTS_SYNC_API_METADATA_CHANGE_LIST_H_
« no previous file with comments | « components/sync/api/metadata_batch.cc ('k') | components/sync/api/mock_model_type_store.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698