<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: State of AJAX</title>
	<atom:link href="http://www.sitepoint.com/blogs/2005/08/21/state-of-ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2005/08/21/state-of-ajax/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sun, 08 Nov 2009 18:39:36 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: asp_funda</title>
		<link>http://www.sitepoint.com/blogs/2005/08/21/state-of-ajax/comment-page-1/#comment-8516</link>
		<dc:creator>asp_funda</dc:creator>
		<pubDate>Wed, 07 Sep 2005 08:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1150#comment-8516</guid>
		<description>&lt;blockquote&gt;
Sometimes you can get away with things like innerHTML (if you’re strictly catering to an audiance that uses the browsers that support it)
&lt;/blockquote&gt;
Etnu, the innerHTML is buggy in IE Mac otherwise it works in all browsers!! :)
see here http://www.quirksmode.org/dom/w3c_html.html#all</description>
		<content:encoded><![CDATA[<blockquote><p>
Sometimes you can get away with things like innerHTML (if you’re strictly catering to an audiance that uses the browsers that support it)
</p></blockquote>
<p>Etnu, the innerHTML is buggy in IE Mac otherwise it works in all browsers!! :)<br />
see here <a href="http://www.quirksmode.org/dom/w3c_html.html#all" rel="nofollow">http://www.quirksmode.org/dom/w3c_html.html#all</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: paulbb</title>
		<link>http://www.sitepoint.com/blogs/2005/08/21/state-of-ajax/comment-page-1/#comment-8225</link>
		<dc:creator>paulbb</dc:creator>
		<pubDate>Tue, 23 Aug 2005 14:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1150#comment-8225</guid>
		<description>In reply to point 3) of Etnu&#039;s list.

It will be interesting to see what Microsofts ensuing &quot;attack&quot; on Macromedia, in the form of Sparkle will lead to.

We should get a better idea of this at the upcomming &quot;Professional Developers Conference&quot; in september, Microsoft will apparently reveal some details of their upcomming plattform.</description>
		<content:encoded><![CDATA[<p>In reply to point 3) of Etnu&#8217;s list.</p>
<p>It will be interesting to see what Microsofts ensuing &#8220;attack&#8221; on Macromedia, in the form of Sparkle will lead to.</p>
<p>We should get a better idea of this at the upcomming &#8220;Professional Developers Conference&#8221; in september, Microsoft will apparently reveal some details of their upcomming plattform.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: z0s0</title>
		<link>http://www.sitepoint.com/blogs/2005/08/21/state-of-ajax/comment-page-1/#comment-8199</link>
		<dc:creator>z0s0</dc:creator>
		<pubDate>Mon, 22 Aug 2005 06:51:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1150#comment-8199</guid>
		<description>Etnu, on what do you base your comment that SOAP and XML-RPC are getting more efficient? The feeling I get when using these technologies is that they instead get more bloated and cumbersome each year.

Re: point 2, a good architect does this &quot;work&quot; once, and once only.  The gains from being able to unit test this stuff - in stark contrast to innerHTML voodoo - far outweigh the cost of slightly more verbose code.</description>
		<content:encoded><![CDATA[<p>Etnu, on what do you base your comment that SOAP and XML-RPC are getting more efficient? The feeling I get when using these technologies is that they instead get more bloated and cumbersome each year.</p>
<p>Re: point 2, a good architect does this &#8220;work&#8221; once, and once only.  The gains from being able to unit test this stuff &#8211; in stark contrast to innerHTML voodoo &#8211; far outweigh the cost of slightly more verbose code.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Etnu</title>
		<link>http://www.sitepoint.com/blogs/2005/08/21/state-of-ajax/comment-page-1/#comment-8197</link>
		<dc:creator>Etnu</dc:creator>
		<pubDate>Mon, 22 Aug 2005 04:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1150#comment-8197</guid>
		<description>That last paragraph is patently false. Apache&#039;s new keepalive system is designed explicitly for delivering small bits of data in rapid-fire succession. And that&#039;s just one piece of technology. SOAP and XML-RPC get more and more efficient every year, and are ideal for this sort of thing. The biggest limitation that AJAX has right now is browsers, namely:

1.) IE still implementing the system using ActiveX, a system that most security experts tell people to disable.

2.) The amount of work necessary to create a large number of elements on a page in a cross-browser fashion, i.e. document.createElement(). Sometimes you can get away with things like innerHTML (if you&#039;re strictly catering to an audiance that uses the browsers that support it), but there are additional limitations there. 

3.) The relative limitations of animation. This could be solved with something like flash, but unfortunately flash wants to be delivered as an application instead of as a piece of media (e.g. an image type).</description>
		<content:encoded><![CDATA[<p>That last paragraph is patently false. Apache&#8217;s new keepalive system is designed explicitly for delivering small bits of data in rapid-fire succession. And that&#8217;s just one piece of technology. SOAP and XML-RPC get more and more efficient every year, and are ideal for this sort of thing. The biggest limitation that AJAX has right now is browsers, namely:</p>
<p>1.) IE still implementing the system using ActiveX, a system that most security experts tell people to disable.</p>
<p>2.) The amount of work necessary to create a large number of elements on a page in a cross-browser fashion, i.e. document.createElement(). Sometimes you can get away with things like innerHTML (if you&#8217;re strictly catering to an audiance that uses the browsers that support it), but there are additional limitations there. </p>
<p>3.) The relative limitations of animation. This could be solved with something like flash, but unfortunately flash wants to be delivered as an application instead of as a piece of media (e.g. an image type).</p>]]></content:encoded>
	</item>
</channel>
</rss>
