<?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: AJAX and Latency</title>
	<atom:link href="http://blog.joshuaeichorn.com/archives/2006/02/13/ajax-and-latency/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.joshuaeichorn.com/archives/2006/02/13/ajax-and-latency/</link>
	<description>The weblog of Joshua Eichorn, AJAX, PHP and Open Source</description>
	<lastBuildDate>Mon, 20 Jun 2011 19:31:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4-alpha</generator>
	<item>
		<title>By: SitePoint Blogs &#187; Two kinds of AJAX: HTML++ vs Client / SOA</title>
		<link>http://blog.joshuaeichorn.com/archives/2006/02/13/ajax-and-latency/comment-page-1/#comment-5750</link>
		<dc:creator>SitePoint Blogs &#187; Two kinds of AJAX: HTML++ vs Client / SOA</dc:creator>
		<pubDate>Wed, 15 Feb 2006 10:44:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joshuaeichorn.com/archives/2006/02/13/ajax-and-latency/#comment-5750</guid>
		<description>[...] In practice this is what everyone&#8217;s doing right now, with varying degrees of success. For many I think the effort and cost to &#8220;go HTML++&#8221; will far outweigh the benefit. Practically think this is best done server-side with tools like HTML_AJAX that do the &#8220;thinking&#8221; for you (side note: while giving this talk, mentioned JPSpan is effectively dead&#8212;HTML_AJAX is, to some extent, it&#8217;s successor&#8212;it&#8217;s a bit like PEAR::SOAP and NuSOAP). [...]</description>
		<content:encoded><![CDATA[<p>[...] In practice this is what everyone&#8217;s doing right now, with varying degrees of success. For many I think the effort and cost to &#8220;go HTML++&#8221; will far outweigh the benefit. Practically think this is best done server-side with tools like HTML_AJAX that do the &#8220;thinking&#8221; for you (side note: while giving this talk, mentioned JPSpan is effectively dead&#8212;HTML_AJAX is, to some extent, it&#8217;s successor&#8212;it&#8217;s a bit like PEAR::SOAP and NuSOAP). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

