<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Retronym for Non-AJAX Apps?</title>
	<atom:link href="http://softwareas.com/retronym-for-non-ajax-apps/feed" rel="self" type="application/rss+xml" />
	<link>http://softwareas.com/retronym-for-non-ajax-apps</link>
	<description>Mahemoff's Podcast/Blog - Web, Programming, Usability from the Author of 'Ajax Design Patterns' (AjaxPatterns.org)</description>
	<lastBuildDate>Sat, 24 Jul 2010 21:06:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben</title>
		<link>http://softwareas.com/retronym-for-non-ajax-apps/comment-page-1#comment-1218</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 25 May 2005 09:22:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareas.com/retronym-for-non-ajax-apps#comment-1218</guid>
		<description>&lt;p&gt;i always thought that, under the somewhat loose common definitions of &quot;static&quot; and &quot;dynamic,&quot; a page that just possessed a form did not constitue dynamism.  rather the page actually had to be able to change itself without the lengthy post operation.  therefore a form that did active numeric validation on a order number field was no more dynamic than one that didn&#039;t. although the page was utilising a script to check data and provide feedback, it wasn&#039;t really changing the page.&lt;/p&gt;

&lt;p&gt;however, a page that updated the Books selection dropdown after the user had chosen a different Author counted as being dynamic, as the page was changing itself.&lt;/p&gt;

&lt;p&gt;maybe instead of removing the &quot;dynamic&quot; property of the current any-server-interaction-means-a-post pages, we could instead include another adjective for the ajaxian style pages, that encompasses that the page is more than dynamic, it is positively racing.  taking your non-sticky retronym (my first encounter with that word by the way!) we could call ajax style pages as &quot;fluid.&quot;  this conjures up images of ever changing html, which is pretty much exactly what&#039;s happening.&lt;/p&gt;

&lt;p&gt;and my favourite of your labels?  i&#039;d have to be a bit cantankerous today and go for the usable website.  mostly because i can forsee a lot of broken sites that just don&#039;t work due to flaws in an implementation of an ajax inspired approach.  after all, not much can go wrong with a bit of plain html, the current dynamic sites have more potential for troubles, so it is easy to expect that the next level of complication will introduce a whole raft of unusable sites.  but then again, as with the early pioneers of dynamic html, it will likely also produce a few brilliant diamonds that make everyone wish they could do just a good job.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>i always thought that, under the somewhat loose common definitions of &#8220;static&#8221; and &#8220;dynamic,&#8221; a page that just possessed a form did not constitue dynamism.  rather the page actually had to be able to change itself without the lengthy post operation.  therefore a form that did active numeric validation on a order number field was no more dynamic than one that didn&#8217;t. although the page was utilising a script to check data and provide feedback, it wasn&#8217;t really changing the page.</p>

<p>however, a page that updated the Books selection dropdown after the user had chosen a different Author counted as being dynamic, as the page was changing itself.</p>

<p>maybe instead of removing the &#8220;dynamic&#8221; property of the current any-server-interaction-means-a-post pages, we could instead include another adjective for the ajaxian style pages, that encompasses that the page is more than dynamic, it is positively racing.  taking your non-sticky retronym (my first encounter with that word by the way!) we could call ajax style pages as &#8220;fluid.&#8221;  this conjures up images of ever changing html, which is pretty much exactly what&#8217;s happening.</p>

<p>and my favourite of your labels?  i&#8217;d have to be a bit cantankerous today and go for the usable website.  mostly because i can forsee a lot of broken sites that just don&#8217;t work due to flaws in an implementation of an ajax inspired approach.  after all, not much can go wrong with a bit of plain html, the current dynamic sites have more potential for troubles, so it is easy to expect that the next level of complication will introduce a whole raft of unusable sites.  but then again, as with the early pioneers of dynamic html, it will likely also produce a few brilliant diamonds that make everyone wish they could do just a good job.</p>]]></content:encoded>
	</item>
</channel>
</rss>
