- From: Scott Wilson <scott.bradley.wilson@gmail.com>
- Date: Tue, 15 Nov 2011 15:52:01 +0000
- To: Robin Berjon <robin@berjon.com>
- Cc: public-native-web-apps@w3.org
On 15 Nov 2011, at 15:30, Robin Berjon wrote: > On Nov 15, 2011, at 15:05 , Scott Wilson wrote: >> As you can see from the implementations we have quite a range of approaches: >> >> - inter-window messaging using HTML5 Web Messaging[3] >> - server-side pub-sub using XMPP, Faye or similar >> - RPC-style reflection and invocation >> - drag and drop with additional semantics >> - OpenAjax Hub pubsub messaging [4] >> - Google Wave Gadget API for state synchronisation [5] >> - Server-sent DOM events for editor state synchronisation [6] > > Have you looked at Web Intents for this? It is probably not a perfect solution in that it is largely meant to broker to generic services (so, say, a "share" service rather than specifically the "Twitter" app) but I think that it addresses quite a few cases for IWC. As a bonus, it'd work the same for widgets, sites, etc. Yes - I think it might fit some of these UCs, particularly those that use a choreography style approach (i.e. topic-based) which I think is conceptually quite similar to intents. I haven't followed the Web Intents thread closely but I read one idea was to add a layer of discovery and message semantics on top of Web Messaging, which also sounds like a good fit. > > -- > Robin Berjon - http://berjon.com/ - @robinberjon >
Received on Tuesday, 15 November 2011 15:52:38 UTC