<?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: Yahoo! JSON API</title>
	<atom:link href="http://ajaxian.com/archives/yahoo-json-api/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/yahoo-json-api</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Brian</title>
		<link>http://ajaxian.com/archives/yahoo-json-api/comment-page-1#comment-44199</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 11 Jul 2006 09:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/yahoo-json-api#comment-44199</guid>
		<description>Found another great example here: http://weblogs.asp.net/mschwarz/archive/2006/07/11/Yahoo_2100_-Web-Services-Request-and-AjaxPro-JSON-Parser-_2D00_-I-love-it_2100_.aspx</description>
		<content:encoded><![CDATA[<p>Found another great example here: <a href="http://weblogs.asp.net/mschwarz/archive/2006/07/11/Yahoo_2100_-Web-Services-Request-and-AjaxPro-JSON-Parser-_2D00_-I-love-it_2100_.aspx" rel="nofollow">http://weblogs.asp.net/mschwarz/archive/2006/07/11/Yahoo_2100_-Web-Services-Request-and-AjaxPro-JSON-Parser-_2D00_-I-love-it_2100_.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Resig</title>
		<link>http://ajaxian.com/archives/yahoo-json-api/comment-page-1#comment-1980</link>
		<dc:creator>John Resig</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/yahoo-json-api#comment-1980</guid>
		<description>Wow... This is huge! This is definitely the next stage of Javascript web application development.

I noticed that if you don&#039;t include a callback, Yahoo returns a proper JSON object (as it should) - a smart move.</description>
		<content:encoded><![CDATA[<p>Wow&#8230; This is huge! This is definitely the next stage of Javascript web application development.</p>
<p>I noticed that if you don&#8217;t include a callback, Yahoo returns a proper JSON object (as it should) &#8211; a smart move.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Brewster</title>
		<link>http://ajaxian.com/archives/yahoo-json-api/comment-page-1#comment-1981</link>
		<dc:creator>Kent Brewster</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/yahoo-json-api#comment-1981</guid>
		<description>Here&#039;s a working example: SpiffY!Search.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a working example: SpiffY!Search.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Purcell</title>
		<link>http://ajaxian.com/archives/yahoo-json-api/comment-page-1#comment-1982</link>
		<dc:creator>Chris Purcell</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/yahoo-json-api#comment-1982</guid>
		<description>Perhaps we should collectively redefine Ajax to mean &quot;Asynchronous Javascript And eXtensibility&quot;? Then mashup-friendliness could be considered baked-in to the definition, and XML dropped (at last).</description>
		<content:encoded><![CDATA[<p>Perhaps we should collectively redefine Ajax to mean &#8220;Asynchronous Javascript And eXtensibility&#8221;? Then mashup-friendliness could be considered baked-in to the definition, and XML dropped (at last).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Manalang</title>
		<link>http://ajaxian.com/archives/yahoo-json-api/comment-page-1#comment-1983</link>
		<dc:creator>Rich Manalang</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/yahoo-json-api#comment-1983</guid>
		<description>Now all we need is a general purpose XML to JSON webservice!</description>
		<content:encoded><![CDATA[<p>Now all we need is a general purpose XML to JSON webservice!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grumpY!</title>
		<link>http://ajaxian.com/archives/yahoo-json-api/comment-page-1#comment-1984</link>
		<dc:creator>grumpY!</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/yahoo-json-api#comment-1984</guid>
		<description>i&#039;m pleased this cute hack came out of my employer, nice to see someone thinking over there. BUT the javascript security features exist for a reason. yes its trivial to set up a middleware proxy, but at least there was an ISP keeping logs on the traffic that passed through it. maybe this is a long-term good, maybe it will force browser vendors and standards groups to apply a real security model to all in-browser scripting.

in the meantime, i use noscript for firefox and recommend you do the same. globally enabling javascript now seems as insane to me as using telnet and rsh.</description>
		<content:encoded><![CDATA[<p>i&#8217;m pleased this cute hack came out of my employer, nice to see someone thinking over there. BUT the javascript security features exist for a reason. yes its trivial to set up a middleware proxy, but at least there was an ISP keeping logs on the traffic that passed through it. maybe this is a long-term good, maybe it will force browser vendors and standards groups to apply a real security model to all in-browser scripting.</p>
<p>in the meantime, i use noscript for firefox and recommend you do the same. globally enabling javascript now seems as insane to me as using telnet and rsh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Atli Thorbjornsson</title>
		<link>http://ajaxian.com/archives/yahoo-json-api/comment-page-1#comment-1985</link>
		<dc:creator>Atli Thorbjornsson</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/yahoo-json-api#comment-1985</guid>
		<description>I am using this approach, talking to a service that can run for 30-40 seconds and returns json progressively so to speak. Wondering whether anyone has an idea on how to make the function calls happen progressively. Right now everything happens at the end once the service is done. The output looks something like this:

doStuff([1,2,3]);
(...4-5 second wait)
doStuff([4,5,6]);
(...4-5 second wait)
doMoreStuff([]);
done();

Obviously I could pack this into an HTML document with enclosing script tags, HTML is rendered progressively so that works fine but that eliminates any chance of access from another domain :) Was hoping to be able to do that without  providing a &quot;proxy&quot; on the other domain
</description>
		<content:encoded><![CDATA[<p>I am using this approach, talking to a service that can run for 30-40 seconds and returns json progressively so to speak. Wondering whether anyone has an idea on how to make the function calls happen progressively. Right now everything happens at the end once the service is done. The output looks something like this:</p>
<p>doStuff([1,2,3]);<br />
(&#8230;4-5 second wait)<br />
doStuff([4,5,6]);<br />
(&#8230;4-5 second wait)<br />
doMoreStuff([]);<br />
done();</p>
<p>Obviously I could pack this into an HTML document with enclosing script tags, HTML is rendered progressively so that works fine but that eliminates any chance of access from another domain :) Was hoping to be able to do that without  providing a &#8220;proxy&#8221; on the other domain</p>
]]></content:encoded>
	</item>
</channel>
</rss>

