Instantiate OriginBoundCertService in relevant places and do plumbing to pass it down to HttpNetw...

chrome/browser/io_thread.h

Index: chrome/browser/io_thread.h
===================================================================
--- chrome/browser/io_thread.h	(revision 94628)
+++ chrome/browser/io_thread.h	(working copy)
@@ -43,6 +43,7 @@
 class HttpAuthHandlerFactory;
 class HttpTransactionFactory;
 class NetworkDelegate;
+class OriginBoundCertService;
 class ProxyConfigService;
 class ProxyScriptFetcher;
 class ProxyService;
@@ -69,6 +70,8 @@
     scoped_ptr<net::NetworkDelegate> system_network_delegate;
     scoped_ptr<net::HostResolver> host_resolver;
     scoped_ptr<net::CertVerifier> cert_verifier;
+    scoped_ptr<net::OriginBoundCertService> proxy_origin_bound_cert_service;
+    scoped_ptr<net::OriginBoundCertService> system_origin_bound_cert_service;

[wtc, 2011/08/08 22:49:20]

These two members should be put next to the related members.

proxy_script_fetcher_xxx_: lines 78-82, and an odd one on line 90
system_xxx_: lines 91-94

But I believe we can use the same origin-bound cert service
object for the proxy script fetcher context and the system
context.  I believe the proxy script fetcher context needs
its own proxy service and anything that depends on a proxy
service; everything else it can share with the system
context.  Please ask eroman or willchan to confirm this.

     scoped_ptr<net::DnsRRResolver> dnsrr_resolver;
     scoped_refptr<net::SSLConfigService> ssl_config_service;
     scoped_ptr<net::HttpAuthHandlerFactory> http_auth_handler_factory;