<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Ajax Middleware</title>
	<atom:link href="http://www.redmonk.com/cote/2007/01/05/ajax-middleware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/</link>
	<description>One foot in the muck, the other in utopia</description>
	<pubDate>Tue, 02 Dec 2008 00:25:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: People Over Process &#187; links for 2008-02-21</title>
		<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-153812</link>
		<dc:creator>People Over Process &#187; links for 2008-02-21</dc:creator>
		<pubDate>Thu, 21 Feb 2008 07:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-153812</guid>
		<description>[...] People Over Process » Ajax Middleware The idea of a &#8220;glass bus&#8221; seems to be coming up more and more now. (tags: riaweeky ajax middleware bus glassbus) [...]</description>
		<content:encoded><![CDATA[<p>[...] People Over Process » Ajax Middleware The idea of a &#8220;glass bus&#8221; seems to be coming up more and more now. (tags: riaweeky ajax middleware bus glassbus) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: People Over Process &#187; Blog Archive &#187; SaaS IT Management</title>
		<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-17397</link>
		<dc:creator>People Over Process &#187; Blog Archive &#187; SaaS IT Management</dc:creator>
		<pubDate>Tue, 20 Mar 2007 21:24:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-17397</guid>
		<description>[...] mashups, composite applications, and other in-browser middle-ware how can you avoid endless [...]</description>
		<content:encoded><![CDATA[<p>[...] mashups, composite applications, and other in-browser middle-ware how can you avoid endless [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-01-13 at 16cards</title>
		<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2967</link>
		<dc:creator>links for 2007-01-13 at 16cards</dc:creator>
		<pubDate>Sat, 13 Jan 2007 15:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2967</guid>
		<description>[...] People Over Process » Blog Archive » Ajax Middleware (tags: GlassBus QEDwiki) [...]</description>
		<content:encoded><![CDATA[<p>[...] People Over Process » Blog Archive » Ajax Middleware (tags: GlassBus QEDwiki) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rod Boothby</title>
		<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2478</link>
		<dc:creator>Rod Boothby</dc:creator>
		<pubDate>Tue, 09 Jan 2007 05:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2478</guid>
		<description>Coté,

Great post.   Thank you.   I completely agree with you about defining a spec and about microformat standards.   Microformat standards are in really early stages at the moment, and the spec for interactions is necessarily going to be fairly complex ... unless something can act as the "glue".   Specifically, I mean two things.   First, a service that takes care of the sequencing, so that things work "automagically" together in the right order.      Second, a service that does the right transforms, takes care of state issues and handles everything from provisioning to routing of federated identity to backup.

My company, Teqlo, is working on providing a web based bus, as a service.   We're in early alpha stage, but "automagical" engine is certainly working!

- Rod</description>
		<content:encoded><![CDATA[<p>Coté,</p>
<p>Great post.   Thank you.   I completely agree with you about defining a spec and about microformat standards.   Microformat standards are in really early stages at the moment, and the spec for interactions is necessarily going to be fairly complex &#8230; unless something can act as the &#8220;glue&#8221;.   Specifically, I mean two things.   First, a service that takes care of the sequencing, so that things work &#8220;automagically&#8221; together in the right order.      Second, a service that does the right transforms, takes care of state issues and handles everything from provisioning to routing of federated identity to backup.</p>
<p>My company, Teqlo, is working on providing a web based bus, as a service.   We&#8217;re in early alpha stage, but &#8220;automagical&#8221; engine is certainly working!</p>
<p>- Rod</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James  Governor</title>
		<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2438</link>
		<dc:creator>James  Governor</dc:creator>
		<pubDate>Mon, 08 Jan 2007 18:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2438</guid>
		<description>problem is jessie's term is running out of steam. ajax middleware? nah... now when JSON is kicking in..</description>
		<content:encoded><![CDATA[<p>problem is jessie&#8217;s term is running out of steam. ajax middleware? nah&#8230; now when JSON is kicking in..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Higgins</title>
		<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2300</link>
		<dc:creator>Bill Higgins</dc:creator>
		<pubDate>Sun, 07 Jan 2007 10:05:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2300</guid>
		<description>I think "Ajax Middleware" is a fine notion.  Middleware does not just mean "app server" or "messaging bus" - it means (to paraphrase Jeff McAffer) "we (the middleware provider) deal with gorp so that you (the application component provider) don't have to".</description>
		<content:encoded><![CDATA[<p>I think &#8220;Ajax Middleware&#8221; is a fine notion.  Middleware does not just mean &#8220;app server&#8221; or &#8220;messaging bus&#8221; - it means (to paraphrase Jeff McAffer) &#8220;we (the middleware provider) deal with gorp so that you (the application component provider) don&#8217;t have to&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tech decentral &#187; links for 2007-01-06</title>
		<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2265</link>
		<dc:creator>tech decentral &#187; links for 2007-01-06</dc:creator>
		<pubDate>Sat, 06 Jan 2007 23:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2265</guid>
		<description>[...] People Over Process » Blog Archive » Ajax Middleware On ajax middleware and glass buses (buses on the client side). (tags: glass-bus ajax middleware browser widgets) [...]</description>
		<content:encoded><![CDATA[<p>[...] People Over Process » Blog Archive » Ajax Middleware On ajax middleware and glass buses (buses on the client side). (tags: glass-bus ajax middleware browser widgets) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danno</title>
		<link>http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2230</link>
		<dc:creator>Danno</dc:creator>
		<pubDate>Sat, 06 Jan 2007 06:52:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/01/05/ajax-middleware/#comment-2230</guid>
		<description>That IBM demo was pretty sweet looking, but when all was said and done, I was left wondering why the user was still forced to do all that clicking manually.

It seemed like you would save yourself a lot of work, but stop just short of the logical conclusion of just letting it run on automagic.

I think I'm thinking "If you've got this glass bus... why do you need people except for the hairy edge cases?"</description>
		<content:encoded><![CDATA[<p>That IBM demo was pretty sweet looking, but when all was said and done, I was left wondering why the user was still forced to do all that clicking manually.</p>
<p>It seemed like you would save yourself a lot of work, but stop just short of the logical conclusion of just letting it run on automagic.</p>
<p>I think I&#8217;m thinking &#8220;If you&#8217;ve got this glass bus&#8230; why do you need people except for the hairy edge cases?&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
