Mojo: Fix two bugs in content handling

mojo/services/public/interfaces/content_handler/content_handler.mojom

Index: mojo/services/public/interfaces/content_handler/content_handler.mojom
diff --git a/mojo/services/public/interfaces/content_handler/content_handler.mojom b/mojo/services/public/interfaces/content_handler/content_handler.mojom
index 1a0ce072f074f5658a95b14e1b69d02127226816..134827909a11b796fe8fd04f2b289827c64c199e 100644
--- a/mojo/services/public/interfaces/content_handler/content_handler.mojom
+++ b/mojo/services/public/interfaces/content_handler/content_handler.mojom
@@ -7,10 +7,15 @@ import "mojo/services/public/interfaces/network/url_loader.mojom"
 
 module mojo {
 

[darin (slow to review), 2014/08/27 06:34:19]

ContentSource perhaps?

My motivation for thinking about different names:
1- ContentHandlerResponse is kind of long
2- ContentHandlerResponse leads to awkward |response->response| code

(this choice doesn't need to block this CL... just food for thought really)

[Aaron Boodman, 2014/08/27 18:26:13]

I like ContentSource, thanks. Changed.

+struct ContentHandlerResponse {
+  URLLoader loader;
+  URLResponse response;
+};
+
 interface ContentHandler {
-  OnConnect(string? url,
-            URLResponse? url_response,
-            ServiceProvider? service_provider);
+  OnConnect(string url,
+            ContentHandlerResponse url_response,
+            ServiceProvider&? service_provider);
 };
 
 }