Plumb NQP to context and to http_proxy_client_socket_pool

net/http/http_network_session.h

Index: net/http/http_network_session.h
diff --git a/net/http/http_network_session.h b/net/http/http_network_session.h
index 1225535f88bd9f7b598a949dac105aae4e32bf2b..1fc6f95e82eb09f9a615b14fb9455db01f380650 100644
--- a/net/http/http_network_session.h
+++ b/net/http/http_network_session.h
@@ -55,6 +55,7 @@ class HttpProxyClientSocketPool;
 class HttpResponseBodyDrainer;
 class HttpServerProperties;
 class NetLog;
+class NetworkQualityEstimator;
 class NetworkThrottleManager;
 class ProxyDelegate;
 class ProxyService;
@@ -188,6 +189,7 @@ class NET_EXPORT HttpNetworkSession : public base::MemoryCoordinatorClient {
     HttpServerProperties* http_server_properties;
     NetLog* net_log;
     SocketPerformanceWatcherFactory* socket_performance_watcher_factory;
+    NetworkQualityEstimator* network_quality_estimator;

[mmenke, 2017/06/05 20:04:26]

Having the bottom layer of the network stack depend on an API that depends on
the top of the network stack (URLRequest) seems like bad API layering to me.

I'm open to other way to avoid this, but one option is to make NQE a virtual
interface, with only observer / get-network-info-type methods, and then make
NQEImpl (Which could completely reasonably be part of URLRequestContext) depend
on URLRequests.

Another option is to make a separate class that NQE either subclasses or that
depends on the NQE, that provides the socket pools with the API they need.

[tbansal1, 2017/06/07 18:13:44]

Done.

 
     // Source of time for QUIC connections.
     QuicClock* quic_clock;