Comments on: TUCON: Tom Laffey and Matt Quinn http://www.column2.com/2007/05/tucon-tom-laffey-and-matt-quinn/ BPM, Enterprise 2.0 and technology trends in business. Fri, 05 Dec 2008 11:12:01 +0000 http://wordpress.org/?v=2.6.2 By: Sandy Kemsley http://www.column2.com/2007/05/tucon-tom-laffey-and-matt-quinn/#comment-4831 Sandy Kemsley Tue, 12 Jun 2007 14:17:08 +0000 http://www.column2.com/2007/05/tucon-tom-laffey-and-matt-quinn/#comment-4831 Kevin, I completely agree. Having come from the integration side of things, I know the problems that will inevitably arise when you start to mashup 3 or more apps at the desktop. I liked Laffey's description, if that wasn't obvious. :) Thanks for the references to the OpenAjax Alliance. I think that TIBCO is making some good contributions here. Kevin, I completely agree. Having come from the integration side of things, I know the problems that will inevitably arise when you start to mashup 3 or more apps at the desktop. I liked Laffey’s description, if that wasn’t obvious. :)
Thanks for the references to the OpenAjax Alliance. I think that TIBCO is making some good contributions here.

]]> By: Kevin Hakman http://www.column2.com/2007/05/tucon-tom-laffey-and-matt-quinn/#comment-4830 Kevin Hakman Sat, 12 May 2007 23:19:57 +0000 http://www.column2.com/2007/05/tucon-tom-laffey-and-matt-quinn/#comment-4830 <p>Re: “Laffey just defined "mashup" as a browser-based event bus, which is an interesting viewpoint, and likely one that resonates better with this audience than the trendier descriptions.” @ <a href="http://www.column2.com" rel="nofollow">http://www.column2.com</a> </p> <p>What’s interesting here is that the underlying *industry standard* for mashups is moving to this client-side bus model. It’s one thing to mashup 2 things: google and craig’s list apartment rentals. It’s another to mash up 5 or more. The point-to-point integration “n-squared” problem arises – just as it does on systems-integration issues where bus architectures are core to addressing the issue.</p> <p>The OpenAjax Alliance is the group setting this standard and a quick scan of the interoperability working group meeting minutes will show that TIBCO’s proposal and contributions are setting the industry standard for a client-side topic/message/event bus specification as the industry standard for getting ajax components to work together in a page. This opens great possibilities for more mature mashups, composite applications, and a vibrant 3rd party market of interoperable ajax gadgets, apps, and controls that can work together in page (by pub/sub events and messages). See openajax.org. Further leading the industry standard TIBCO is donating the core of the TIBCO PageBus to the OpenAjax Alliance for inclusion in its open source implementation of the spec: the OpenAjax Hub. That works extends original work TIBCO did in collaboration with The Dojo Toolkit for the baseline pub/sub event system. The most recent contribution adds topics and wildcards in topics to the implementation to support a broader set of use cases more easily.</p> <p>--Kevin Hakman, TIBCO Software Inc.</p> Re: “Laffey just defined “mashup” as a browser-based event bus, which is an interesting viewpoint, and likely one that resonates better with this audience than the trendier descriptions.” @ <a href=”http://www.column2.com” rel=”nofollow”>http://www.column2.com</a>

What’s interesting here is that the underlying *industry standard* for mashups is moving to this client-side bus model. It’s one thing to mashup 2 things: google and craig’s list apartment rentals. It’s another to mash up 5 or more. The point-to-point integration “n-squared” problem arises – just as it does on systems-integration issues where bus architectures are core to addressing the issue.

The OpenAjax Alliance is the group setting this standard and a quick scan of the interoperability working group meeting minutes will show that TIBCO’s proposal and contributions are setting the industry standard for a client-side topic/message/event bus specification as the industry standard for getting ajax components to work together in a page. This opens great possibilities for more mature mashups, composite applications, and a vibrant 3rd party market of interoperable ajax gadgets, apps, and controls that can work together in page (by pub/sub events and messages). See openajax.org. Further leading the industry standard TIBCO is donating the core of the TIBCO PageBus to the OpenAjax Alliance for inclusion in its open source implementation of the spec: the OpenAjax Hub. That works extends original work TIBCO did in collaboration with The Dojo Toolkit for the baseline pub/sub event system. The most recent contribution adds topics and wildcards in topics to the implementation to support a broader set of use cases more easily.

–Kevin Hakman, TIBCO Software Inc.

]]>