<?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: The API is the Application</title>
	<atom:link href="http://www.newthink.net/2008/10/20/the-api-is-the-application/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.newthink.net/2008/10/20/the-api-is-the-application/</link>
	<description>Less Talk. More Do.</description>
	<lastBuildDate>Thu, 22 Jul 2010 15:10:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ash Christopher</title>
		<link>http://www.newthink.net/2008/10/20/the-api-is-the-application/comment-page-1/#comment-1719</link>
		<dc:creator>Ash Christopher</dc:creator>
		<pubDate>Wed, 31 Dec 2008 05:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.newthink.net/?p=90#comment-1719</guid>
		<description>REST implies stateless data, so it wouldn&#039;t really be useful for applications such as wizards. It could be used to populate data when interacting with a wizard.

Data that was entered on a previous screen would be presumably stored in the session somewhere, and that data may be passed to a REST resource which would return data to populate the page.</description>
		<content:encoded><![CDATA[<p>REST implies stateless data, so it wouldn&#8217;t really be useful for applications such as wizards. It could be used to populate data when interacting with a wizard.</p>
<p>Data that was entered on a previous screen would be presumably stored in the session somewhere, and that data may be passed to a REST resource which would return data to populate the page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://www.newthink.net/2008/10/20/the-api-is-the-application/comment-page-1/#comment-1718</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Wed, 31 Dec 2008 05:28:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.newthink.net/?p=90#comment-1718</guid>
		<description>Hmmm... sounds like a reasonable way to do something simple, but how do you handle stateful applications. i.e. What happens now is different from what happened earlier based on a change that was made. A simple Request (What is the weather like in Waterloo, ON) and allowes for a simple response. If you need to process a stream of interactions (i.e. a Wizard) it sounds like you&#039;d have to do something else other than REST to make that happen.</description>
		<content:encoded><![CDATA[<p>Hmmm&#8230; sounds like a reasonable way to do something simple, but how do you handle stateful applications. i.e. What happens now is different from what happened earlier based on a change that was made. A simple Request (What is the weather like in Waterloo, ON) and allowes for a simple response. If you need to process a stream of interactions (i.e. a Wizard) it sounds like you&#8217;d have to do something else other than REST to make that happen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
