Pass content-type resources to web intents. Goes through download, then invokes the p…

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..fa127dadfb2466098046190b33b8fa68ae73a2d0 100644
--- a/content/public/browser/web_intents_dispatcher.h
+++ b/content/public/browser/web_intents_dispatcher.h
@@ -17,6 +17,7 @@ struct WebIntentData;
 namespace content {
 
 class WebContents;
+class WebContentsDelegate;
 
 // This class is the coordinator for dispatching web intents and seeing that
 // return messages are sent to the correct invoking context. The WebContents
@@ -59,6 +60,13 @@ class CONTENT_EXPORT WebIntentsDispatcher {
   virtual void RegisterReplyNotification(const ReplyNotification& closure) = 0;
 };
 
+// Create and dispatch an internal (embedder-triggered) intent. This will create
+// a new dispatcher with the passed intent payload |data| and dispatch it to the
+// delegate of the provided WebContents |target|.
+CONTENT_EXPORT void DispatchInternalIntent(

[jam, 2012/03/29 02:33:51]

perhaps this should be a static Create inside WebIntensDispatcher?  i.e.

static WebIntensDispatcher* Create(const webkit_glue::WebIntentData& data);

then whoever calls this can call WebIntentDispatch themselves.

i say this because this is really a creator function, and this is the pattern we
use in the rest of the content api

[Greg Billock, 2012/03/29 17:33:03]

Sounds good. I was trying to keep dispatching within content, but it really is a
one-liner.

On 2012/03/29 02:33:51, John Abd-El-Malek wrote:

+    const webkit_glue::WebIntentData& data,
+    WebContents* target);
+
 }  // namespace content
 
 #endif  // CONTENT_PUBLIC_BROWSER_WEB_INTENTS_DISPATCHER_H_