<?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: New Look and Feel for Charles</title>
	<atom:link href="http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/feed/" rel="self" type="application/rss+xml" />
	<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/</link>
	<description>Two specialist fields: weaponry and space medicine. An interesting combination, don't you think?</description>
	<pubDate>Wed, 07 Jan 2009 19:40:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Marcelo Serpa</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-246</link>
		<dc:creator>Marcelo Serpa</dc:creator>
		<pubDate>Sun, 10 Dec 2006 16:49:54 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-246</guid>
		<description>Hey Karl, really good improvements on the UI, you've gone ahead my expectations, thanks for that and keep up the great work!</description>
		<content:encoded><![CDATA[<p>Hey Karl, really good improvements on the UI, you&#8217;ve gone ahead my expectations, thanks for that and keep up the great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-152</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Thu, 16 Nov 2006 01:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-152</guid>
		<description>Great! Thank you very much for your help.</description>
		<content:encoded><![CDATA[<p>Great! Thank you very much for your help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TLJ</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-151</link>
		<dc:creator>TLJ</dc:creator>
		<pubDate>Thu, 16 Nov 2006 00:30:31 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-151</guid>
		<description>It works now. Awesome! Thanks! :)</description>
		<content:encoded><![CDATA[<p>It works now. Awesome! Thanks! <img src='http://xk72.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-150</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Thu, 16 Nov 2006 00:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-150</guid>
		<description>Thanks for that. The problem was the ()s around the value in the X-JSON header. I've fixed that so it now works with your link above. Please download the beta again.</description>
		<content:encoded><![CDATA[<p>Thanks for that. The problem was the ()s around the value in the X-JSON header. I&#8217;ve fixed that so it now works with your link above. Please download the beta again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TLJ</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-149</link>
		<dc:creator>TLJ</dc:creator>
		<pubDate>Wed, 15 Nov 2006 22:18:37 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-149</guid>
		<description>Try this: http://alltid.org/team/65179/

Click the "add to compare" link under "tools" in the left menu. It returns status codes in the X-JSON HTTP header, and a plain text string in the body.

Doesn't seem like the new Charles version detects it. I use the OSX version, btw.</description>
		<content:encoded><![CDATA[<p>Try this: <a href="http://alltid.org/team/65179/" rel="nofollow">http://alltid.org/team/65179/</a></p>
<p>Click the &#8220;add to compare&#8221; link under &#8220;tools&#8221; in the left menu. It returns status codes in the X-JSON HTTP header, and a plain text string in the body.</p>
<p>Doesn&#8217;t seem like the new Charles version detects it. I use the OSX version, btw.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-148</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Wed, 15 Nov 2006 22:07:25 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-148</guid>
		<description>Try downloading the new beta (from the same URL). I've made it so that if a header is present it will check to see if the body contains JSON data. It should also show a view parsing the JSON header value. I haven't tested this against a live site yet; are you able to send me a link to a site I can test against?</description>
		<content:encoded><![CDATA[<p>Try downloading the new beta (from the same URL). I&#8217;ve made it so that if a header is present it will check to see if the body contains JSON data. It should also show a view parsing the JSON header value. I haven&#8217;t tested this against a live site yet; are you able to send me a link to a site I can test against?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TLJ</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-147</link>
		<dc:creator>TLJ</dc:creator>
		<pubDate>Wed, 15 Nov 2006 22:00:45 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-147</guid>
		<description>In most requests the X-JSON and body are the same, but there might be cases where the the body is blank, or even HTML or XML. 

I suggest that if you see the X-JSON header, make the JSON view the default, but have the option of ASCII/hex. Just like when viewing XML.</description>
		<content:encoded><![CDATA[<p>In most requests the X-JSON and body are the same, but there might be cases where the the body is blank, or even HTML or XML. </p>
<p>I suggest that if you see the X-JSON header, make the JSON view the default, but have the option of ASCII/hex. Just like when viewing XML.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-146</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Wed, 15 Nov 2006 21:08:56 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-146</guid>
		<description>Thanks for that, I wasn't aware of the X-JSON header. It looks like the header actually contains JSON data itself, so it should be decoded. I'll add that in. Are you seeing JSON data in the X-JSON header and in the response body? Perhaps I can make the viewer look for JSON data in the body inspite of the mime type if the X-JSON header is present.</description>
		<content:encoded><![CDATA[<p>Thanks for that, I wasn&#8217;t aware of the X-JSON header. It looks like the header actually contains JSON data itself, so it should be decoded. I&#8217;ll add that in. Are you seeing JSON data in the X-JSON header and in the response body? Perhaps I can make the viewer look for JSON data in the body inspite of the mime type if the X-JSON header is present.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TLJ</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-145</link>
		<dc:creator>TLJ</dc:creator>
		<pubDate>Wed, 15 Nov 2006 20:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-145</guid>
		<description>I send it as text/html, and should probably change it to text/json. So thanks for making me aware of that. From the searches I've done now, it seems like some other sites sends its JSON as text/html. But that's our own fault. You probably shouldn't try to fetch JSON from text/html.

There's one thing you can look for though - the X-JSON HTTP header. I don't know how "official" that header is, but it's used by at least Prototype, and probably some other JS frameworks. Wouldn't hurt to include detection of JSON through that.</description>
		<content:encoded><![CDATA[<p>I send it as text/html, and should probably change it to text/json. So thanks for making me aware of that. From the searches I&#8217;ve done now, it seems like some other sites sends its JSON as text/html. But that&#8217;s our own fault. You probably shouldn&#8217;t try to fetch JSON from text/html.</p>
<p>There&#8217;s one thing you can look for though - the X-JSON HTTP header. I don&#8217;t know how &#8220;official&#8221; that header is, but it&#8217;s used by at least Prototype, and probably some other JS frameworks. Wouldn&#8217;t hurt to include detection of JSON through that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/comment-page-1/#comment-144</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Wed, 15 Nov 2006 18:05:55 +0000</pubDate>
		<guid isPermaLink="false">http://xk72.com/blog/2006/11/15/new-look-and-feel-for-charles/#comment-144</guid>
		<description>The JSON viewer looks at the mime type of the response to decide whether to activate. It's looking for text/json or application/json, but it will try to autodetect JSON if the mime type if application/javascript or text/plain. Unfortunately there's some discrepancy in the mime types people are using! Can you tell me what mime type you're seeing on your JSON data?

The JSON viewer will display a tree, much like the XML tree... makes it easier to see the structure of the data.</description>
		<content:encoded><![CDATA[<p>The JSON viewer looks at the mime type of the response to decide whether to activate. It&#8217;s looking for text/json or application/json, but it will try to autodetect JSON if the mime type if application/javascript or text/plain. Unfortunately there&#8217;s some discrepancy in the mime types people are using! Can you tell me what mime type you&#8217;re seeing on your JSON data?</p>
<p>The JSON viewer will display a tree, much like the XML tree&#8230; makes it easier to see the structure of the data.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
