Get rid of URLLoaderFactory in browser-side case

content/common/url_loader.mojom

Index: content/common/url_loader.mojom
diff --git a/content/common/url_loader.mojom b/content/common/url_loader.mojom
index 53b7521310516182449a01f6742898b4e7d90f3e..a04995966ed0c7e15eb98a92002cf8c3f913ce5e 100644
--- a/content/common/url_loader.mojom
+++ b/content/common/url_loader.mojom
@@ -31,6 +31,14 @@ enum RequestPriority {
 
 // Destroying a URLLoader will cancel the associated request.
 interface URLLoader {
+  // Starts loading and binds the given |loader| request with this loader.
+  // This method is intended to be called in C++ impl (as it is not
+  // possible to Start this before |loader| binding in mojo layer), and
+  // is not necessary to call this if the loader is created and stgarted by
+  // URLLoaderFactory.
+  // It is not valid to call this method more than once.
+  Start(associated URLLoader& loader, URLLoaderClient client);

[kinuko, 2017/06/05 09:44:23]

Having a method like this in mojom feels a bit weird, while for C++ use cases
this makes things handier.

What do you think? Any alternative suggestions also really welcome.

+
   // If the associated request has |auto_follow_redirects| set to false,
   // then upon receiving an URLResponse with a non-NULL |redirect_url| field,
   // |FollowRedirect| may be called to load the URL indicated by the redirect.