Initial PlzNavigate RDH-side logic.

content/browser/loader/navigation_url_loader_impl.cc

+// Copyright 2014 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.
+
+#include "content/browser/loader/navigation_url_loader_impl.h"
+
+#include "content/browser/loader/navigation_url_loader_core.h"
+
+namespace content {
+
+NavigationURLLoaderImpl::NavigationURLLoaderImpl(

[nasko, 2014/09/24 21:15:34]

Why do we need the separation of Impl and Core, when the Impl doesn't do much?

[davidben, 2014/10/03 16:27:52]

Impl is uniquely owned and lives on the UI-thread. Core is ref-counted and lives
on both. Yeah, I'm not very happy with how much machinery is involved here. I do
feel the exposed API should be uniquely owned; the fact that there's craziness
across threads should be hidden from the caller. And then there needs to be some
IO-thread object to plug into the loader stack and plumb signals back to the
UI-thread object, so I think we'll need at least two. The Core/ResourceHandler
separation is slightly weird but probably can't easily be resolved without
ResourceLoader ownership getting tidied up.

+    BrowserContext* browser_context,
+    int64 frame_tree_node_id,
+    const NavigationRequestInfo& request_info,
+    ResourceRequestBody* request_body,
+    NavigationURLLoader::Delegate* delegate)
+    : core_(new NavigationURLLoaderCore) {
+  core_->set_delegate(delegate);
+  core_->StartRequest(browser_context, frame_tree_node_id, request_info,
+                      request_body);
+}
+
+NavigationURLLoaderImpl::~NavigationURLLoaderImpl() {
+  core_->Cancel();
+  core_->set_delegate(NULL);
+}
+
+void NavigationURLLoaderImpl::FollowRedirect() {
+  core_->FollowRedirect();
+}
+
+}  // namespace content