Pass command line arguments onto platform apps which provide the right intent.

content/public/browser/web_intents_dispatcher.h

Index: content/public/browser/web_intents_dispatcher.h
diff --git a/content/public/browser/web_intents_dispatcher.h b/content/public/browser/web_intents_dispatcher.h
index 36d55e0a633b08e53eeb5d8758c9de85421d7003..b05def5400b4691d5652068d5398d7b1e4a27b2d 100644
--- a/content/public/browser/web_intents_dispatcher.h
+++ b/content/public/browser/web_intents_dispatcher.h
@@ -7,6 +7,7 @@
 
 #include "base/callback.h"
 #include "content/common/content_export.h"
+#include "content/public/browser/render_view_host.h"
 #include "webkit/glue/web_intent_reply_data.h"
 
 namespace webkit_glue {
@@ -59,6 +60,14 @@ class CONTENT_EXPORT WebIntentsDispatcher {
   virtual void RegisterReplyNotification(const ReplyNotification& closure) = 0;
 };
 
+// This function is used when the intent provider render view is already known,

[Greg Billock, 2012/03/28 14:21:02]

Why not use the internal dispatcher, so the return pathways are hooked up? You
can simply not set the callback, but that'll give you a hook if you need it.

[benwells, 2012/03/29 03:29:18]

OK, that makes sense. So instead of this function there would be a function like
WebIntentsDispatcher CreateInternalWebIntentsDispatcher(WebIntentData).

After creating one of these in the browser process I'd then call
DispatchIntent(web_contents).

+// and there is no need to register a callback. Instead the intent data just
+// needs to be dispatched 'one-way' to the RenderViewHost. |intent_data| is the
+// WebIntentData to inject. |render_view_host| is the RenderViewHost to inject
+// the data into, and must not be NULL.
+CONTENT_EXPORT void DirectDispatchIntent(webkit_glue::WebIntentData intent_data,
+                                         RenderViewHost* render_view_host);
+
 }  // namespace content
 
 #endif  // CONTENT_PUBLIC_BROWSER_WEB_INTENTS_DISPATCHER_H_