<?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: Facebook Application Logistics for Team Development</title>
	<atom:link href="http://www.pathf.com/blogs/2008/04/facebook-applic/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/04/facebook-applic/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Sat, 22 Nov 2008 00:22:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Pathfinder Development &#187; Getting Started with Facebooker</title>
		<link>http://www.pathf.com/blogs/2008/04/facebook-applic/#comment-2702</link>
		<dc:creator>Pathfinder Development &#187; Getting Started with Facebooker</dc:creator>
		<pubDate>Wed, 30 Jul 2008 20:57:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=22#comment-2702</guid>
		<description>[...] When you're developing Facebook apps, having a remote server to develop on is completely integral. If you're developing in FBML (and in the new version of the Facebook profile system, FBML is practically required), to see the results of your hard work you'll have to actually allow the Facebook servers to interpret your markup. That means they need access to your development machine, or you need a tunnel from your development machine to a remote server that's already accessible from the Internet, or you set up a staging server by following the advice of Noel Rappin's excellent blog post, Facebook Application Logistics for Team Development. [...]</description>
		<content:encoded><![CDATA[<p>[...] When you&#8217;re developing Facebook apps, having a remote server to develop on is completely integral. If you&#8217;re developing in FBML (and in the new version of the Facebook profile system, FBML is practically required), to see the results of your hard work you&#8217;ll have to actually allow the Facebook servers to interpret your markup. That means they need access to your development machine, or you need a tunnel from your development machine to a remote server that&#8217;s already accessible from the Internet, or you set up a staging server by following the advice of Noel Rappin&#8217;s excellent blog post, Facebook Application Logistics for Team Development. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
