<?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: More on Rich Internet Applications</title>
	<atom:link href="http://blog.jameslin.name/2007/05/13/more-on-rich-internet-applications/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jameslin.name/2007/05/13/more-on-rich-internet-applications/</link>
	<description>Jimmy Lin&#039;s blog</description>
	<lastBuildDate>Sun, 14 Aug 2011 18:55:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Daniel Azuma</title>
		<link>http://blog.jameslin.name/2007/05/13/more-on-rich-internet-applications/comment-page-1/#comment-251</link>
		<dc:creator>Daniel Azuma</dc:creator>
		<pubDate>Thu, 24 May 2007 05:40:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jameslin.name/2007/05/13/more-on-rich-internet-applications/#comment-251</guid>
		<description>Dave Thomas made an interesting point during his keynote at RailsConf.

He traced some of the history of computing. First you have dumb stateless terminals (e.g. the IBM 3270) that connect to a central mainframe via half duplex connections, displaying forms but submitting them back to the server and relying on it to do all the processing. Then this evolved into terminals that are able to do full duplex real-time interaction with the mainframe, maybe a character at a time, but still relying on it to perform computations. Finally, &quot;smart&quot; terminals evolved that were able to store state and perform some computations on the client side.

Then, in the early 90s, the next step in the evolution of computing arrived: the browser, a dumb stateless interface connected half-duplex to a central server, capable of displaying forms but submitting the results back to the server and relying on it to do all the processing. Then you have ajax, a full-duplex communication in which the client remains dumb and stateless but at least a little more interactive. And so forth.

In his words, &quot;There is no practical difference between the [web] browser and the [IBM] 3270, except that the browser can display better porn.&quot;

Interesting to think that maybe all we&#039;ve been doing so far with internet applications has been to go around in circles and reinvent the 70s.</description>
		<content:encoded><![CDATA[<p>Dave Thomas made an interesting point during his keynote at RailsConf.</p>
<p>He traced some of the history of computing. First you have dumb stateless terminals (e.g. the IBM 3270) that connect to a central mainframe via half duplex connections, displaying forms but submitting them back to the server and relying on it to do all the processing. Then this evolved into terminals that are able to do full duplex real-time interaction with the mainframe, maybe a character at a time, but still relying on it to perform computations. Finally, &#8220;smart&#8221; terminals evolved that were able to store state and perform some computations on the client side.</p>
<p>Then, in the early 90s, the next step in the evolution of computing arrived: the browser, a dumb stateless interface connected half-duplex to a central server, capable of displaying forms but submitting the results back to the server and relying on it to do all the processing. Then you have ajax, a full-duplex communication in which the client remains dumb and stateless but at least a little more interactive. And so forth.</p>
<p>In his words, &#8220;There is no practical difference between the [web] browser and the [IBM] 3270, except that the browser can display better porn.&#8221;</p>
<p>Interesting to think that maybe all we&#8217;ve been doing so far with internet applications has been to go around in circles and reinvent the 70s.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

