<?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: Third Step into the Open Social world</title>
	<atom:link href="http://www.chabotc.com/javascript/third-step-into-the-open-social-world/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chabotc.com/javascript/third-step-into-the-open-social-world/</link>
	<description>Random storms of thoughts</description>
	<lastBuildDate>Thu, 11 Mar 2010 05:01:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: chabotc</title>
		<link>http://www.chabotc.com/javascript/third-step-into-the-open-social-world/comment-page-1/#comment-7690</link>
		<dc:creator>chabotc</dc:creator>
		<pubDate>Wed, 20 Feb 2008 09:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.chabotc.com/generic/third-step-into-the-open-social-world/#comment-7690</guid>
		<description>Hey Akash,

Yes the API has been changed (though the old calls still work too), and the calls have been moved into a nicer opensocial.* namespace, for instance its now opensocial.makeRequest() to fetch remote content; The workings are the same, but it does make it a bit more readable though :-)

However this class still works perfectly (though i&#039;ll update it soonish to use the new API style), and it still a nice convenience to have this functionality wrapped in an easy to use library so you don&#039;t have to rewrite the same thing over and over again :-)</description>
		<content:encoded><![CDATA[<p>Hey Akash,</p>
<p>Yes the API has been changed (though the old calls still work too), and the calls have been moved into a nicer opensocial.* namespace, for instance its now opensocial.makeRequest() to fetch remote content; The workings are the same, but it does make it a bit more readable though <img src='http://www.chabotc.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>However this class still works perfectly (though i&#8217;ll update it soonish to use the new API style), and it still a nice convenience to have this functionality wrapped in an easy to use library so you don&#8217;t have to rewrite the same thing over and over again <img src='http://www.chabotc.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Akash Xavier J</title>
		<link>http://www.chabotc.com/javascript/third-step-into-the-open-social-world/comment-page-1/#comment-7689</link>
		<dc:creator>Akash Xavier J</dc:creator>
		<pubDate>Wed, 20 Feb 2008 03:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.chabotc.com/generic/third-step-into-the-open-social-world/#comment-7689</guid>
		<description>Aren&#039;t those _IG_* API calls a part of iGoogle and I suppose OpenSocial has its own set of calls?
There was once a talk in the shindig mailing list that these IG calls will be removed since they aren&#039;t a part of the spec?</description>
		<content:encoded><![CDATA[<p>Aren&#8217;t those _IG_* API calls a part of iGoogle and I suppose OpenSocial has its own set of calls?<br />
There was once a talk in the shindig mailing list that these IG calls will be removed since they aren&#8217;t a part of the spec?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
