network service: Plumbing to get URLLoaderFactory to renderer on nav commit

content/browser/frame_host/render_frame_host_impl.cc

Index: content/browser/frame_host/render_frame_host_impl.cc
diff --git a/content/browser/frame_host/render_frame_host_impl.cc b/content/browser/frame_host/render_frame_host_impl.cc
index 485c02170811614575315bdd046054db829d3a93..caa9a42def266c37b36472cceeafef57418f3be7 100644
--- a/content/browser/frame_host/render_frame_host_impl.cc
+++ b/content/browser/frame_host/render_frame_host_impl.cc
@@ -3019,9 +3019,12 @@ void RenderFrameHostImpl::CommitNavigation(
   const GURL body_url = body.get() ? body->GetURL() : GURL();
   const ResourceResponseHead head = response ?
       response->head : ResourceResponseHead();
-  Send(new FrameMsg_CommitNavigation(routing_id_, head, body_url,
-                                     handle.release(), common_params,
-                                     request_params));
+  FrameMsg_CommitDataNetworkService_Params commit_data;
+  commit_data.handle = handle.release();
+  // TODO(scottmg): Pass a factory for SW, etc. once we have one.
+  commit_data.url_loader_factory = mojo::MessagePipeHandle();

[kinuko, 2017/05/02 03:37:50]

When network service is enabled we already have one (that might not really work
yet but anyways), is that right?

[scottmg, 2017/05/02 15:19:22]

Right, when --enable-network-service is on, the renderer currently uses the
connection manager to connect directly to the network service. Once we figure
out where the other endpoint should live for SW, we can pass the url loader
through here, and then this per-frame one will override the global connection
straight to the network in the renderer.

+  Send(new FrameMsg_CommitNavigation(routing_id_, head, body_url, commit_data,
+                                     common_params, request_params));
 
   // If a network request was made, update the Previews state.
   if (ShouldMakeNetworkRequestForURL(common_params.url) &&