Seculative resource prefetching for URLs CL.

chrome/browser/profiles/profile_io_data.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_BROWSER_PROFILES_PROFILE_IO_DATA_H_
 #define CHROME_BROWSER_PROFILES_PROFILE_IO_DATA_H_
 #pragma once
 
 #include <string>
 
@@ skipping 26 matching lines @@
 class CookieStore;
 class FraudulentCertificateReporter;
 class HttpTransactionFactory;
 class ServerBoundCertService;
 class ProxyConfigService;
 class ProxyService;
 class SSLConfigService;
 class TransportSecurityState;
 }  // namespace net
 
+namespace predictors {
+class ResourcePrefetchPredictor;
+}  // namespace predictors
+
 namespace policy {
 class URLBlacklistManager;
 }  // namespace policy
 
 // Conceptually speaking, the ProfileIOData represents data that lives on the IO
 // thread that is owned by a Profile, such as, but not limited to, network
 // objects like CookieMonster, HttpTransactionFactory, etc.  Profile owns
 // ProfileIOData, but will make sure to delete it on the IO thread (except
 // possibly in unit tests where there is no IO thread).
 class ProfileIOData {
@@ skipping 107 matching lines @@
 #endif
 
     scoped_refptr<ProtocolHandlerRegistry> protocol_handler_registry;
     // We need to initialize the ProxyConfigService from the UI thread
     // because on linux it relies on initializing things through gconf,
     // and needs to be on the main thread.
     scoped_ptr<net::ProxyConfigService> proxy_config_service;
     // 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;
   };
 
   explicit ProfileIOData(bool is_incognito);
 
   static std::string GetSSLSessionCacheShard();
 
   void InitializeOnUIThread(Profile* profile);
   void ApplyProfileParamsToContext(ChromeURLRequestContext* context) const;
 
@@ skipping 169 matching lines @@
 
   // TODO(jhawkins): Remove once crbug.com/102004 is fixed.
   bool initialized_on_UI_thread_;
 
   bool is_incognito_;
 
   DISALLOW_COPY_AND_ASSIGN(ProfileIOData);
 };
 
 #endif  // CHROME_BROWSER_PROFILES_PROFILE_IO_DATA_H_