Implement Invalidator::Acknowledge

chrome/browser/sync/glue/android_invalidator_bridge_proxy.cc

Index: chrome/browser/sync/glue/android_invalidator_bridge_proxy.cc
diff --git a/chrome/browser/sync/glue/android_invalidator_bridge_proxy.cc b/chrome/browser/sync/glue/android_invalidator_bridge_proxy.cc
index 236ed44f3b4698b4818f3157f2d0af8eb8dfe56d..619c76d76838e5b3230e36f09cfa2005caf55b75 100644
--- a/chrome/browser/sync/glue/android_invalidator_bridge_proxy.cc
+++ b/chrome/browser/sync/glue/android_invalidator_bridge_proxy.cc
@@ -40,6 +40,12 @@ void AndroidInvalidatorBridgeProxy::UnregisterHandler(
   bridge_->UnregisterHandler(handler);
 }
 
+void AndroidInvalidatorBridgeProxy::Acknowledge(
+    const invalidation::ObjectId& id,
+    const syncer::AckHandle& ack_handle) {
+  bridge_->Acknowledge(id, ack_handle);
+}

[Pete Williamson, 2013/02/16 01:41:06]

Does it make sense to add push messaging to android?  They already have GCM. 
(or maybe this is not needed to add push messaging, but just needed because we
added push messaging to the rest of the system.)

[dcheng, 2013/02/22 02:51:30]

Android doesn't support extensions. If this changes, we may have to revisit
this.

+
 void AndroidInvalidatorBridgeProxy::SetUniqueId(const string& unique_id) {
   bridge_->SetUniqueId(unique_id);
 }