<?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: JSONView Updated to 0.1b3</title>
	<atom:link href="http://benhollis.net/blog/2009/03/15/jsonview-updated-to-01b3/feed/" rel="self" type="application/rss+xml" />
	<link>http://benhollis.net/blog/2009/03/15/jsonview-updated-to-01b3/</link>
	<description>News about BenHollis.net and articles about Ben&#039;s interests</description>
	<lastBuildDate>Fri, 03 Sep 2010 02:00:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Ben Hollis</title>
		<link>http://benhollis.net/blog/2009/03/15/jsonview-updated-to-01b3/comment-page-1/#comment-9068</link>
		<dc:creator>Ben Hollis</dc:creator>
		<pubDate>Fri, 17 Apr 2009 05:27:18 +0000</pubDate>
		<guid isPermaLink="false">http://brh.numbera.com/blog/?p=324#comment-9068</guid>
		<description>Hey riz, you can follow the discussion about that on the Google Code project issue tracker: http://code.google.com/p/jsonview/issues/detail?id=12

You&#039;re right that it wouldn&#039;t be hard, but the issue is that there&#039;s really only one correct content type for JSON, and that&#039;s &quot;application/json&quot;. It&#039;s not like JavaScript which has a handful of valid types. So I&#039;d recommend fixing your server rather than extending JSONView to handle invalid cases.</description>
		<content:encoded><![CDATA[<p>Hey riz, you can follow the discussion about that on the Google Code project issue tracker: <a href="http://code.google.com/p/jsonview/issues/detail?id=12" rel="nofollow">http://code.google.com/p/jsonview/issues/detail?id=12</a></p>
<p>You&#8217;re right that it wouldn&#8217;t be hard, but the issue is that there&#8217;s really only one correct content type for JSON, and that&#8217;s &#8220;application/json&#8221;. It&#8217;s not like JavaScript which has a handful of valid types. So I&#8217;d recommend fixing your server rather than extending JSONView to handle invalid cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: riz</title>
		<link>http://benhollis.net/blog/2009/03/15/jsonview-updated-to-01b3/comment-page-1/#comment-9066</link>
		<dc:creator>riz</dc:creator>
		<pubDate>Thu, 16 Apr 2009 18:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://brh.numbera.com/blog/?p=324#comment-9066</guid>
		<description>Hi there! I love the idea of JSONView, but one thing I&#039;d like to change is that I&#039;d like JSONView to support not only &quot;application/json&quot; content types, but &quot;text/json&quot; as well. 

I am not familiar enough with nsIStreamConverter, but if you point me in the right direction, I can try doing it myself in Google code (and post back the changes to you). It sounds like you&#039;d have to register another whole stream converter for &quot;text/json&quot;.</description>
		<content:encoded><![CDATA[<p>Hi there! I love the idea of JSONView, but one thing I&#8217;d like to change is that I&#8217;d like JSONView to support not only &#8220;application/json&#8221; content types, but &#8220;text/json&#8221; as well. </p>
<p>I am not familiar enough with nsIStreamConverter, but if you point me in the right direction, I can try doing it myself in Google code (and post back the changes to you). It sounds like you&#8217;d have to register another whole stream converter for &#8220;text/json&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
