Use mojo for Chrome Loading, Part 1

content/common/url_loader_factory.mojom

Index: content/common/url_loader_factory.mojom
diff --git a/ios/web/shell/test/shell_test.mm b/content/common/url_loader_factory.mojom
similarity index 58%
copy from ios/web/shell/test/shell_test.mm
copy to content/common/url_loader_factory.mojom
index 5b4cddc172c1c4cafc6884d64c1f2cf5e1514915..6876e3ce1c1a89630980bc664296f4b0f968632c 100644
--- a/ios/web/shell/test/shell_test.mm
+++ b/content/common/url_loader_factory.mojom
@@ -2,11 +2,10 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-#import <UIKit/UIKit.h>
-#import <XCTest/XCTest.h>
+module content.mojom;
 
-@interface EmptyFile : NSObject
-@end
+import "url_loader.mojom";
 
-@implementation EmptyFile
-@end
+interface URLLoaderFactory {
+  CreateURLLoader(URLLoader& loader);

[mmenke, 2016/05/26 15:18:49]

I don't suppose we can combine with with Start?  i.e. take a request_id,
URLRequest, and URLLoaderClient?  I'm not set on a combined create+start being
the ideal API, but it makes ownership semantecs for the URLLoader sane.  If,
once the RDH is using a purely mojo API, you want to change how things work, and
have a reasonably ownership model to go with it, I'm certainly fine with
changing it.

[yhirano, 2016/05/27 11:30:34]

I think it is at least non-trivial work. content::URLLoaderFactoryImpl is bound
to UI thread, and if we pass a client, it will be bound to that thread, too.

[mmenke, 2016/05/27 15:39:26]

Can we move URLLoaderFactoryImpl over to the UI thread?  Make it owned by the
RDH?  (Or make the RDH itself the factory?)

[mmenke, 2016/05/27 15:41:04]

OVer to the IO thread, rather.

[yhirano, 2016/06/07 08:16:57]

Done.

+};