<?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: Book Review &#8211; Ajax Patterns and Best Practices</title>
	<atom:link href="http://ajaxian.com/archives/book-review-ajax-patterns-and-best-practices/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/book-review-ajax-patterns-and-best-practices</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: softwareoutsouring</title>
		<link>http://ajaxian.com/archives/book-review-ajax-patterns-and-best-practices/comment-page-1#comment-260052</link>
		<dc:creator>softwareoutsouring</dc:creator>
		<pubDate>Mon, 17 Dec 2007 10:52:54 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1452#comment-260052</guid>
		<description>So it means that no patternes related to JSON are covered in this book? I was looking for it, but if has only clinged to xml, better I stop now.</description>
		<content:encoded><![CDATA[<p>So it means that no patternes related to JSON are covered in this book? I was looking for it, but if has only clinged to xml, better I stop now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ajaxhash</title>
		<link>http://ajaxian.com/archives/book-review-ajax-patterns-and-best-practices/comment-page-1#comment-260050</link>
		<dc:creator>ajaxhash</dc:creator>
		<pubDate>Mon, 17 Dec 2007 10:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1452#comment-260050</guid>
		<description>I agree with Gaz, coz of my own experience with xml that made ajax a too difficult experience for me. Now I feel more relaxed with JSON and the best part is its usage for web services from Yahoo, Google and others. So no need to go through those proxy hacks for cross server ajax.</description>
		<content:encoded><![CDATA[<p>I agree with Gaz, coz of my own experience with xml that made ajax a too difficult experience for me. Now I feel more relaxed with JSON and the best part is its usage for web services from Yahoo, Google and others. So no need to go through those proxy hacks for cross server ajax.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaz Elms</title>
		<link>http://ajaxian.com/archives/book-review-ajax-patterns-and-best-practices/comment-page-1#comment-154273</link>
		<dc:creator>Gaz Elms</dc:creator>
		<pubDate>Mon, 30 Oct 2006 14:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1452#comment-154273</guid>
		<description>I&#039;m not surprised he is saying xml is the best format for data interchange  - only because it is easy to create at the back end.

However I never use xml any more, it is bloated and cannot be easily converted to JS objects. I have written a json creator in c# which makes light work of creating json</description>
		<content:encoded><![CDATA[<p>I&#8217;m not surprised he is saying xml is the best format for data interchange  &#8211; only because it is easy to create at the back end.</p>
<p>However I never use xml any more, it is bloated and cannot be easily converted to JS objects. I have written a json creator in c# which makes light work of creating json</p>
]]></content:encoded>
	</item>
</channel>
</rss>

