Consistently use notifications from component updater w/ on-demand PNaCl.

chrome/browser/component_updater/component_updater_service.cc

Index: chrome/browser/component_updater/component_updater_service.cc
diff --git a/chrome/browser/component_updater/component_updater_service.cc b/chrome/browser/component_updater/component_updater_service.cc
index 804885582df9a2b4c893b5fc161e377c760fa879..0962c41da9a4b50745199d33d886d7f6c50d4acb 100644
--- a/chrome/browser/component_updater/component_updater_service.cc
+++ b/chrome/browser/component_updater/component_updater_service.cc
@@ -984,6 +984,15 @@ void CrxUpdateService::DoneInstalling(const std::string& component_id,
   ScheduleNextRun(false);
 }
 
+bool ComponentUpdateService::IsUpdateNotificationForComponent(
+    const content::NotificationSource& src,
+    const CrxComponent& component) {
+  std::string id =
+      HexStringToID(StringToLowerASCII(base::HexEncode(&component.pk_hash[0],
+                                       component.pk_hash.size()/2)));
+  return content::Source<std::string>(src)->compare(id) == 0;
+}
+
 // The component update factory. Using the component updater as a singleton
 // is the job of the browser process.
 ComponentUpdateService* ComponentUpdateServiceFactory(