sync: Remove ModelTypeInvalidationMap

Removes the definition and all uses of ModelTypeInvalidationMap.

The ModelTypeInvalidationMap was useful only for sync-related
invalidations.  Its existence made sense when sync was the only client
for invalidations.  Now that we have many invalidations clients, it
makes sense to replace it with the more generic ObjectIdInvalidationMap.

The reason for doing this now is that the ObjectIdInvalidationMap will
soon be modified to be incompatible with the current definition of
ModelTypeInvalidationMap.  In order to support trickles it will be
modified to allow it to contain several invalidations per ObjectId.
Although it would have been possible to maintain compatibility by making
a corresponding modification to ModelTypeInvalidationMap, there's really
no point in having two invalidation map types.  In the long run, it
makes more sense to deprecate ModelTypeInvalidationMap.

BUG=233437

Review URL: https://chromiumcodereview.appspot.com/23238005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221025 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 0 insertions, 11 deletions

diff --git a/sync/internal_api/public/engine/model_safe_worker.cc b/sync/internal_api/public/engine/model_safe_worker.cc
index 5c91715..eb3fc1f 100644
--- a/sync/internal_api/public/engine/model_safe_worker.cc
+++ b/sync/internal_api/public/engine/model_safe_worker.cc
@@ -31,17 +31,6 @@ std::string ModelSafeRoutingInfoToString(
   return json;
 }
 
-ModelTypeInvalidationMap ModelSafeRoutingInfoToInvalidationMap(
-    const ModelSafeRoutingInfo& routes,
-    const std::string& payload) {
-  ModelTypeInvalidationMap invalidation_map;
-  for (ModelSafeRoutingInfo::const_iterator i = routes.begin();
-       i != routes.end(); ++i) {
-    invalidation_map[i->first].payload = payload;
-  }
-  return invalidation_map;
-}
-
 ModelTypeSet GetRoutingInfoTypes(const ModelSafeRoutingInfo& routing_info) {
   ModelTypeSet types;
   for (ModelSafeRoutingInfo::const_iterator it = routing_info.begin();