Component updater on-demand logic with ResourceThrottle

chrome/browser/component_updater/crx_update_item.h

Index: chrome/browser/component_updater/crx_update_item.h
===================================================================
--- chrome/browser/component_updater/crx_update_item.h	(revision 231370)
+++ chrome/browser/component_updater/crx_update_item.h	(working copy)
@@ -9,10 +9,13 @@
 #include <vector>
 
 #include "base/basictypes.h"
+#include "base/memory/weak_ptr.h"
 #include "base/time/time.h"
 #include "base/version.h"
 #include "chrome/browser/component_updater/component_updater_service.h"
 
+class CUResourceThrottle;
+
 // This is the one and only per-item state structure. Designed to be hosted
 // in a std::vector or a std::list. The two main members are |component|
 // which is supplied by the the component updater client and |status| which
@@ -102,6 +105,8 @@
   int diff_error_code;
   int diff_extra_code1;
 
+  std::vector<base::WeakPtr<CUResourceThrottle>> throttles;

[Sorin Jianu, 2013/10/31 18:43:58]

what is the opinion in the codebase relative to >> vs. > > in the context above?
Most of the code seems to be using > >.

[cpu_(ooo_6.6-7.5), 2013/10/31 21:36:08]

Good catch. VS can handle but did not compile on *nix for this reason. Changed.

+
   CrxUpdateItem();
   ~CrxUpdateItem();