Seculative resource prefetching for URLs CL.

chrome/browser/profiles/profile_io_data.h

Index: chrome/browser/profiles/profile_io_data.h
diff --git a/chrome/browser/profiles/profile_io_data.h b/chrome/browser/profiles/profile_io_data.h
index f4702bbb65673bba496ececdeda67c292c177537..2adaede03641072c4af966e6a2e8ec773530eb07 100644
--- a/chrome/browser/profiles/profile_io_data.h
+++ b/chrome/browser/profiles/profile_io_data.h
@@ -44,6 +44,10 @@ class SSLConfigService;
 class TransportSecurityState;
 }  // namespace net
 
+namespace predictors {
+class ResourcePrefetchPredictor;
+}  // namespace predictors
+
 namespace policy {
 class URLBlacklistManager;
 }  // namespace policy
@@ -171,6 +175,8 @@ class ProfileIOData {
     // The profile this struct was populated from. It's passed as a void* to
     // ensure it's not accidently used on the IO thread. Before using it on the
     // UI thread, call ProfileManager::IsValidProfile to ensure it's alive.
+    scoped_refptr<predictors::ResourcePrefetchPredictor>

[dominich, 2012/05/24 16:07:53]

comment applies to |profile| below. So move this.

[dominich, 2012/05/24 16:07:53]

this is the source of my confusion: in Profile IO data you have a ref to the
UI-based Predictor. This is then passed to the NetworkDelegate which creates an
IO-based Observer which communicates with the UI-based predictor.

Why not have the Observer created and owned by the IO data and have it get the
reference to the Predictor as necessary?

[Shishir, 2012/05/30 01:07:51]

Done.

[Shishir, 2012/05/30 01:07:51]

Done.

+        resource_prefetch_predictor_;
     void* profile;
   };