<?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: JSON2.js vs Prototype</title>
	<atom:link href="http://assanka.net/content/tech/2009/09/02/json2-js-vs-prototype/feed/" rel="self" type="application/rss+xml" />
	<link>http://assanka.net/content/tech/2009/09/02/json2-js-vs-prototype/</link>
	<description>Just another Arb-assk2009003.turmeric.assanka.com Blogs weblog</description>
	<lastBuildDate>Fri, 25 Nov 2011 16:18:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ragaskar</title>
		<link>http://assanka.net/content/tech/2009/09/02/json2-js-vs-prototype/comment-page-1/#comment-19</link>
		<dc:creator>ragaskar</dc:creator>
		<pubDate>Sun, 24 Jan 2010 19:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://assanka.net/content/tech/?p=5#comment-19</guid>
		<description>Update: 

It ended up being easier to let Prototype do its own thing -- I ended up looking for Prototype in the window and toJSON on the object and calling that if it exists. Additionally, in some browsers you may not be able to depend on the JSON.stringify implementation being exactly the same as the one in json2.js. I posted about this issue on my blog: http://agaskar.com/post/349461220/json-stringify-bug-with-native-ff-implementation</description>
		<content:encoded><![CDATA[<p>Update: </p>
<p>It ended up being easier to let Prototype do its own thing &#8212; I ended up looking for Prototype in the window and toJSON on the object and calling that if it exists. Additionally, in some browsers you may not be able to depend on the JSON.stringify implementation being exactly the same as the one in json2.js. I posted about this issue on my blog: <a href="http://agaskar.com/post/349461220/json-stringify-bug-with-native-ff-implementation" rel="nofollow">http://agaskar.com/post/349461220/json-stringify-bug-with-native-ff-implementation</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ragaskar</title>
		<link>http://assanka.net/content/tech/2009/09/02/json2-js-vs-prototype/comment-page-1/#comment-18</link>
		<dc:creator>ragaskar</dc:creator>
		<pubDate>Sat, 16 Jan 2010 05:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://assanka.net/content/tech/?p=5#comment-18</guid>
		<description>Thanks for these notes; it helped me figure out where Prototype was going wrong. That said, this replacer fn seems to only work for shallow objects -- if I have an array with an object that itself contains an array, it will be stringified. I&#039;m working on fixing that problem and if I come up with a solution that is any good I will post it here.</description>
		<content:encoded><![CDATA[<p>Thanks for these notes; it helped me figure out where Prototype was going wrong. That said, this replacer fn seems to only work for shallow objects &#8212; if I have an array with an object that itself contains an array, it will be stringified. I&#8217;m working on fixing that problem and if I come up with a solution that is any good I will post it here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

