<?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"
	>
<channel>
	<title>Comments on: Mashups versus Facebook</title>
	<atom:link href="http://www.pathf.com/blogs/2007/07/mashups-versus/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/07/mashups-versus/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 05 Dec 2008 11:06:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Rainhut</title>
		<link>http://www.pathf.com/blogs/2007/07/mashups-versus/#comment-410</link>
		<dc:creator>Rainhut</dc:creator>
		<pubDate>Sat, 08 Sep 2007 04:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=307#comment-410</guid>
		<description>&lt;p&gt;Check out the Stagegold video player as an example of a true widget on facebook.  &lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Check out the Stagegold video player as an example of a true widget on facebook.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rainhut</title>
		<link>http://www.pathf.com/blogs/2007/07/mashups-versus/#comment-409</link>
		<dc:creator>Rainhut</dc:creator>
		<pubDate>Sat, 08 Sep 2007 04:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=307#comment-409</guid>
		<description>&lt;p&gt;A true facebook widget is written in actionscript. That's the only way to get to their apis from the client. Javascript would cause too many security issues. The Facebook markup language (FMBL) makes it seem that they support various languages like C# .net etc, but it does nothing but add complexity to a system that has only one true way to build a dynamic widget. &lt;/p&gt;

&lt;p&gt;  &lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>A true facebook widget is written in actionscript. That&#8217;s the only way to get to their apis from the client. Javascript would cause too many security issues. The Facebook markup language (FMBL) makes it seem that they support various languages like C# .net etc, but it does nothing but add complexity to a system that has only one true way to build a dynamic widget. </p></p>
]]></content:encoded>
	</item>
</channel>
</rss>
