<?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: Enterprise Ajax 14 &#8211; Nitobi &#8211; Ajax and Analysts</title>
	<atom:link href="http://blogs.nitobi.com/andre/index.php/2006/09/22/enterprise-ajax-14-nitobi-ajax-and-analysts/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.nitobi.com/andre/index.php/2006/09/22/enterprise-ajax-14-nitobi-ajax-and-analysts/</link>
	<description>AKA Captain AJAX - Keepin' it clean and Livin' the Dream!</description>
	<lastBuildDate>Tue, 17 Jan 2012 09:35:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Software As She&apos;s Developed - Ajax Functionality and Usability Patterns - Podcast 4 of 4: Functionality Patterns</title>
		<link>http://blogs.nitobi.com/andre/index.php/2006/09/22/enterprise-ajax-14-nitobi-ajax-and-analysts/comment-page-1/#comment-4091</link>
		<dc:creator>Software As She&apos;s Developed - Ajax Functionality and Usability Patterns - Podcast 4 of 4: Functionality Patterns</dc:creator>
		<pubDate>Sat, 23 Sep 2006 18:25:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.nitobi.com/andre/?p=240#comment-4091</guid>
		<description>[...] Dedicated to the Nitobians, whose last podcast inspired me to crank another one out again. Recent events suggest it may cost me $5000 to appear on their podcast again, and as Andre points out in this podcast, the same applies for them appearing on my podcast. Thus, my simple proposal would be: [...]</description>
		<content:encoded><![CDATA[<p>[...] Dedicated to the Nitobians, whose last podcast inspired me to crank another one out again. Recent events suggest it may cost me $5000 to appear on their podcast again, and as Andre points out in this podcast, the same applies for them appearing on my podcast. Thus, my simple proposal would be: [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

