<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>QuirksBlog</title>	<link>http://tc.eserver.org/publisher/QuirksBlog</link>
	<description>A listing of works published by QuirksBlog in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-10 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>QuirksBlog</title>
		<link>http://tc.eserver.org/dir/QuirksBlog</link>
	</image>
	<item>
		<title>The AJAX response: XML, HTML, or JSON?</title>
		<link>http://tc.eserver.org/35074.html</link>
		<guid>http://tc.eserver.org/35074.html</guid>
		<description>Since my last AJAX project I&apos;ve increasingly been wondering about the &quot;ideal&quot; output format for the AJAX response. Once you&apos;ve succesfully fired an AJAX request, what sort of response should the server give? An XML document? An HTML snippet? A JSON string which is converted to a JavaScript object? Or something else? In this entry I&apos;d like to discuss the three formats, with examples, and ask you which format you&apos;ve used in your practical AJAX applications.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/QuirksBlog.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>