PlzNavigate: implement CommitNavigation on the browser side

content/browser/frame_host/render_frame_host_manager.h

Index: content/browser/frame_host/render_frame_host_manager.h
diff --git a/content/browser/frame_host/render_frame_host_manager.h b/content/browser/frame_host/render_frame_host_manager.h
index 9a6ded5e5166272d009fcb5e7c498ab671b53886..b64d8b4d94e605b3d073f6d585c4f79197d03049 100644
--- a/content/browser/frame_host/render_frame_host_manager.h
+++ b/content/browser/frame_host/render_frame_host_manager.h
@@ -42,7 +42,10 @@ class RenderWidgetHostDelegate;
 class RenderWidgetHostView;
 class TestWebContents;
 class WebUIImpl;
+struct CommitNavigationParams;
+struct CoreNavigationParams;
 struct NavigationBeforeCommitInfo;
+struct RequestNavigationParams;
 
 // Manages RenderFrameHosts for a FrameTreeNode.  This class acts as a state
 // machine to make cross-process navigations in a frame possible.
@@ -315,16 +318,20 @@ class CONTENT_EXPORT RenderFrameHostManager : public NotificationObserver {
 
   // PlzNavigate: sends a RequestNavigation IPC to the renderer to ask it to
   // navigate. If no live renderer is present, then the navigation request will
-  // be sent directly to the ResourceDispatcherHost.
-  bool RequestNavigation(const NavigationEntryImpl& entry,
-                         const FrameMsg_Navigate_Params& navigate_params);
+  // be sent directly to the ResourceDispatcherHost. Takes ownership of
+  // |core_params| and |commit_params| to send them to the appropriate renderer
+  // when the navigation is ready to commit.
+  bool RequestNavigation(scoped_ptr<CoreNavigationParams> core_params,
+                         const RequestNavigationParams& request_params,
+                         scoped_ptr<CommitNavigationParams> commit_params);
 
   // PlzNavigate: Used to start a navigation. OnBeginNavigation is called
   // directly by RequestNavigation when there is no live renderer. Otherwise, it
   // is called following a BeginNavigation IPC from the renderer (which in
   // browser-initiated navigation also happens after RequestNavigation has been
   // called).
-  void OnBeginNavigation(const FrameHostMsg_BeginNavigation_Params& params);
+  void OnBeginNavigation(const FrameHostMsg_BeginNavigation_Params& params,
+                         const CoreNavigationParams& core_params);
 
   // PlzNavigate: Called when a navigation request has received a response, to
   // select a renderer to use for the navigation.
@@ -535,6 +542,11 @@ class CONTENT_EXPORT RenderFrameHostManager : public NotificationObserver {
   // it commits.
   scoped_ptr<NavigationRequest> navigation_request_;
 
+  // PlzNavigate: Holds info that should be sent to the renderer when the

[Charlie Reis, 2014/09/19 23:12:31]

Do these have the same lifetime as navigation_request_?  Should they live there
instead?  (If not, please clarify how their lifetime differs in the comment.)

[clamy, 2014/09/23 21:13:25]

I moved them inside navigation_request_. They did not have the same lifetime
initially, but it is probably better if they do.

+  // navigation is about to commit.
+  scoped_ptr<CoreNavigationParams> core_navigation_params_;
+  scoped_ptr<CommitNavigationParams> commit_navigation_params_;

[Charlie Reis, 2014/09/19 23:12:31]

(I'm still a bit nervous about storing request-specific state in RFHM, with the
risk of it being overwritten by a different navigation request.  If this data
lived with the request on the IO thread and was then passed back, then RFHM
would be stateless with respect to ResourceRequests.  The thread hop seems
problematic, though, and we probably don't want a map of requests indexed by
navigation_request_id.  Perhaps storing it here is ok for the time being.)

[clamy, 2014/09/23 21:13:25]

I think storing them in the NavigationRequest makes it simpler, especially as
davidben@ has a CL that clarifies thread hops involving the NavigationRequest.

+
   base::WeakPtrFactory<RenderFrameHostManager> weak_factory_;
 
   DISALLOW_COPY_AND_ASSIGN(RenderFrameHostManager);