Implement Invalidator::Acknowledge

chrome/browser/extensions/api/push_messaging/push_messaging_invalidation_handler.cc

Index: chrome/browser/extensions/api/push_messaging/push_messaging_invalidation_handler.cc
diff --git a/chrome/browser/extensions/api/push_messaging/push_messaging_invalidation_handler.cc b/chrome/browser/extensions/api/push_messaging/push_messaging_invalidation_handler.cc
index cee8305e0cfb75a753fec60d39575e490084fb5a..c3dec490166ea9929b51eef917bcf7bb2a9cd429 100644
--- a/chrome/browser/extensions/api/push_messaging/push_messaging_invalidation_handler.cc
+++ b/chrome/browser/extensions/api/push_messaging/push_messaging_invalidation_handler.cc
@@ -131,6 +131,7 @@ void PushMessagingInvalidationHandler::OnIncomingInvalidation(
                                          &subchannel)) {
       delegate_->OnMessage(extension_id, subchannel, it->second.payload);

[akalin, 2012/10/19 13:27:16]

Question: Is this synchronous?  i.e., can we ack immediately after this?

[dcheng, 2012/10/19 19:38:11]

Doing this properly is somewhat harder, as this involves a message to the
renderer and then being notified when the renderer is finished--the glue for
this does not currently exist. I do plan on improving this outside of this CL;
the current implementation is just to preserve legacy behavior.

     }
+    service_->AcknowledgeInvalidation(it->first, it->second.ack_handle);
   }
 }