Re: Means for allowing triggering of all registered handlers

We have always tried to stay away from this, of seemed like a ux nightmare
and at the time only suited to applications that share content. (If you
have other use cases please let us know)

The way we would suggest solving it is for apps like Hootsuite etc to
manage this as they already broadcast to multiple networks.
On 22 Aug 2012 19:32, "Brett Zamir" <brettz9@yahoo.com> wrote:

>  Hi,
>
> Could a means be added to Web Intents to allow ALL matching registered
> handlers to be executed (with an event to indicate completion)?
>
> I would think one should be able to use such a means to make one's
> application extensible via "plug-ins" whose code could add overlays or
> behaviors (e.g., to allow 3rd parties to add their own context menus to
> one's web app), of course bearing in mind security concerns (as with single
> service usage), or the approach could be used for publish-subscribe, etc.
>
> For example, one might have a third party client app to request Twitter,
> Facebook, Google Mail, etc. (e.g., if the user had set such a preference to
> allow this behavior at these sites), to pass on messages which could be
> shown and handled in a common interface (like POP or IMAP email).
>
> The "persistent connections" approach (
> http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html#persistent-connections) could also enable development of a multi-service chatting application
> with discovery of new services.
>
> Thanks,
> Brett
>
>