<?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: 10 Things To Know About JSON (JSON Javascript Examples)</title>
	<atom:link href="http://codytaylor.org/2009/06/10-things-to-know-about-json-json-javascript-examples.html/feed" rel="self" type="application/rss+xml" />
	<link>http://codytaylor.org/2009/06/10-things-to-know-about-json-json-javascript-examples.html</link>
	<description>From Cody Taylor.</description>
	<lastBuildDate>Thu, 13 Oct 2011 06:41:44 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Reedo</title>
		<link>http://codytaylor.org/2009/06/10-things-to-know-about-json-json-javascript-examples.html/comment-page-1#comment-2698</link>
		<dc:creator>Reedo</dc:creator>
		<pubDate>Thu, 04 Jun 2009 17:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://codytaylor.org/?p=14091#comment-2698</guid>
		<description>The 4th thing (ease of human reading/writing) is more a matter of preference. When there&#039;s much nesting, I find XML easier to read than JSON (get ready to count those braces and brackets!). And while there are some excellent editors for XML, there are fewer out there for JSON.

The 2nd thing (speed) is due more to the minimalist syntax than the Javascript compatibility, I believe. But the gain in network speed vs. XML isn&#039;t as impressive when gzip-encoding the data, which everyone should be doing.</description>
		<content:encoded><![CDATA[<p>The 4th thing (ease of human reading/writing) is more a matter of preference. When there&#8217;s much nesting, I find XML easier to read than JSON (get ready to count those braces and brackets!). And while there are some excellent editors for XML, there are fewer out there for JSON.</p>
<p>The 2nd thing (speed) is due more to the minimalist syntax than the Javascript compatibility, I believe. But the gain in network speed vs. XML isn&#8217;t as impressive when gzip-encoding the data, which everyone should be doing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cody Taylor</title>
		<link>http://codytaylor.org/2009/06/10-things-to-know-about-json-json-javascript-examples.html/comment-page-1#comment-2683</link>
		<dc:creator>Cody Taylor</dc:creator>
		<pubDate>Thu, 04 Jun 2009 03:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://codytaylor.org/?p=14091#comment-2683</guid>
		<description>Thanks for the comment. Hmm JSON injection eh? Cross domain capabilities? Could be interesting.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment. Hmm JSON injection eh? Cross domain capabilities? Could be interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noah</title>
		<link>http://codytaylor.org/2009/06/10-things-to-know-about-json-json-javascript-examples.html/comment-page-1#comment-2682</link>
		<dc:creator>Noah</dc:creator>
		<pubDate>Thu, 04 Jun 2009 03:25:03 +0000</pubDate>
		<guid isPermaLink="false">http://codytaylor.org/?p=14091#comment-2682</guid>
		<description>But it is okay to use executable code in JSON within an application, in fact it is probably easier and more efficient than the way you are doing it now (assuming you&#039;re not using JSON heavily).</description>
		<content:encoded><![CDATA[<p>But it is okay to use executable code in JSON within an application, in fact it is probably easier and more efficient than the way you are doing it now (assuming you&#8217;re not using JSON heavily).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noah</title>
		<link>http://codytaylor.org/2009/06/10-things-to-know-about-json-json-javascript-examples.html/comment-page-1#comment-2681</link>
		<dc:creator>Noah</dc:creator>
		<pubDate>Thu, 04 Jun 2009 03:17:02 +0000</pubDate>
		<guid isPermaLink="false">http://codytaylor.org/?p=14091#comment-2681</guid>
		<description>Please be aware that you should NOT put executable code into JSON objects and pass them to other runtimes using AJAX.  That is how JSON injection occurs and most JSON libraries and implementations deter that behavior.</description>
		<content:encoded><![CDATA[<p>Please be aware that you should NOT put executable code into JSON objects and pass them to other runtimes using AJAX.  That is how JSON injection occurs and most JSON libraries and implementations deter that behavior.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

