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

chrome/browser/component_updater/component_updater_service.h

Index: chrome/browser/component_updater/component_updater_service.h
diff --git a/chrome/browser/component_updater/component_updater_service.h b/chrome/browser/component_updater/component_updater_service.h
index c0975454efa6fe5103d25b403163692801e25230..cbc216ada55fd981fbc54efe225ead6ed328499a 100644
--- a/chrome/browser/component_updater/component_updater_service.h
+++ b/chrome/browser/component_updater/component_updater_service.h
@@ -20,6 +20,10 @@ class DictionaryValue;
 class FilePath;
 }
 
+namespace content {
+class NotificationSource;
+}
+
 class ComponentPatcher;
 
 // Component specific installers must derive from this class and implement
@@ -156,6 +160,12 @@ class ComponentUpdateService {
   // via the Install() hook.
   virtual Status CheckForUpdateSoon(const CrxComponent& component) = 0;
 
+  // Return true if a NOTIFICATION_COMPONENT_UPDATE_FOUND or
+  // NOTIFICATION_COMPONENT_UPDATE_READY is for the given component.
+  static bool IsUpdateNotificationForComponent(
+      const content::NotificationSource& src,
+      const CrxComponent& component);

[Sorin Jianu, 2013/07/03 21:17:32]

This static member seems out of place in the definition of
ComponentUpdateService, which is a abstract class. Having a statric member here
could also make mocking of the class difficult in the future.

[jvoung (off chromium), 2013/07/03 22:51:51]

Ah good point. Changed to non-static.

+
   virtual ~ComponentUpdateService() {}
 };