<?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: UIConf: Ajax Everywhere</title>
	<atom:link href="http://bokardo.com/archives/uiconf-ajax-everywhere/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/uiconf-ajax-everywhere/</link>
	<description>A Blog about Social Web Design</description>
	<pubDate>Fri, 05 Sep 2008 22:57:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: tkouts</title>
		<link>http://bokardo.com/archives/uiconf-ajax-everywhere/#comment-1773</link>
		<dc:creator>tkouts</dc:creator>
		<pubDate>Wed, 19 Oct 2005 15:36:23 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/uiconf-ajax-everywhere/#comment-1773</guid>
		<description>I wouldn't say that AJAX as a technology is something totally new. I would only agree that it is new as a term. The first application I saw using AJAX was Microsoft's Outlook Web Access, about 4 years ago. I'm surprised that Microsoft didn't invest more on this technology.</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t say that AJAX as a technology is something totally new. I would only agree that it is new as a term. The first application I saw using AJAX was Microsoft&#8217;s Outlook Web Access, about 4 years ago. I&#8217;m surprised that Microsoft didn&#8217;t invest more on this technology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://bokardo.com/archives/uiconf-ajax-everywhere/#comment-1720</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 12 Oct 2005 00:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/uiconf-ajax-everywhere/#comment-1720</guid>
		<description>The name is new, but the technology isn't. Speaking as someone who works at an organization that must rely on stable technology for enterprise applications, all of the pieces of AJAX are proven.

But AJAX needs good hardware on both sides of the line to perform well. We've recently reached that point.

Having a few examples to lead the way certainly helped. As did a catchy buzzword.</description>
		<content:encoded><![CDATA[<p>The name is new, but the technology isn&#8217;t. Speaking as someone who works at an organization that must rely on stable technology for enterprise applications, all of the pieces of AJAX are proven.</p>
<p>But AJAX needs good hardware on both sides of the line to perform well. We&#8217;ve recently reached that point.</p>
<p>Having a few examples to lead the way certainly helped. As did a catchy buzzword.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Bidochko</title>
		<link>http://bokardo.com/archives/uiconf-ajax-everywhere/#comment-1710</link>
		<dc:creator>Andrew Bidochko</dc:creator>
		<pubDate>Mon, 10 Oct 2005 21:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/uiconf-ajax-everywhere/#comment-1710</guid>
		<description>Completely agree with Andrew. AJAX is just a mix of already known things - this is great.

From other point of view any web-application can be easily modified to work as web-service once it was written using AJAX(this means that UI was completely separated from business logic).</description>
		<content:encoded><![CDATA[<p>Completely agree with Andrew. AJAX is just a mix of already known things - this is great.</p>
<p>From other point of view any web-application can be easily modified to work as web-service once it was written using AJAX(this means that UI was completely separated from business logic).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://bokardo.com/archives/uiconf-ajax-everywhere/#comment-1709</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 10 Oct 2005 20:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/uiconf-ajax-everywhere/#comment-1709</guid>
		<description>One reason might be that although the UE aspects are (arguably) tricky to integrate nicely into applications, Ajax is technically pretty simple. It's much easier for developers to say yes to an idea when it doesn't really involve much new to learn or new conditions to worry about. Grab one of the several good Ajax javascript libraries, make some very minor changes to the way pages are generated, and you're good to go.</description>
		<content:encoded><![CDATA[<p>One reason might be that although the UE aspects are (arguably) tricky to integrate nicely into applications, Ajax is technically pretty simple. It&#8217;s much easier for developers to say yes to an idea when it doesn&#8217;t really involve much new to learn or new conditions to worry about. Grab one of the several good Ajax javascript libraries, make some very minor changes to the way pages are generated, and you&#8217;re good to go.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<div  style="display:none; width=0px; height=0px" >
</div>