<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The Down Side of AJAX</title>
	<link>http://www.willeitner.org/2006/10/27/the-down-side-of-ajax/?tid=commentsrss2feed</link>
	<description>Internet Marketing Insights</description>
	<pubDate>Mon, 06 Feb 2012 14:18:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Jimmy Zimmerman</title>
		<link>http://www.willeitner.org/2006/10/27/the-down-side-of-ajax/#comment-14?tid=commentsrss2feed</link>
		<pubDate>Sat, 28 Oct 2006 16:23:25 +0000</pubDate>
		<guid>http://www.willeitner.org/2006/10/27/the-down-side-of-ajax/#comment-14?tid=commentsrss2feed</guid>
					<description>This is a classic example of AJAX gone wrong. This would be my advice for whoever first developed that site: Just because you can doesn't mean you should.

Ajax is better suited for form interaction and when you need to save things in the background on the server. It shouldn't be used to navigate through your content, especially when you want the search engines to crawl it. Keeping Google in mind is always important when designing new sites.

You know that already, but I'm just puttin' in my two cents.</description>
		<content:encoded><![CDATA[<p>This is a classic example of AJAX gone wrong. This would be my advice for whoever first developed that site: Just because you can doesn&#8217;t mean you should.</p>
<p>Ajax is better suited for form interaction and when you need to save things in the background on the server. It shouldn&#8217;t be used to navigate through your content, especially when you want the search engines to crawl it. Keeping Google in mind is always important when designing new sites.</p>
<p>You know that already, but I&#8217;m just puttin&#8217; in my two cents.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

