<?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: XMLHttpRequest Vs. iFrames</title>
	<atom:link href="http://ajaxian.com/archives/xmlhttprequest-vs-iframes/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: 0k</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-272397</link>
		<dc:creator>0k</dc:creator>
		<pubDate>Sat, 28 Mar 2009 16:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-272397</guid>
		<description>I think either DOM injection or iframes will do the job. At least as far as the bandwidth and server horse power won&#039;t let a ajax page refresh or evolve to let say show, for example, an animation where the info to be drawn homogeneously may be rendered/sent by the server really fast. We may play with that at this time on our local configs, but for drawing basic htm content remotely... I have to say that iframes are much easier/faster and cross-plateform to implement for the moment. Regarding the back-forward thing, I fully agree with Atli but something tells me that back-forwarding with anchor hashes, data cached in each iframes is really fast and enjoying on a navigation point of view so I would prefer to solve the headache with iframes or DOM based framework.</description>
		<content:encoded><![CDATA[<p>I think either DOM injection or iframes will do the job. At least as far as the bandwidth and server horse power won&#8217;t let a ajax page refresh or evolve to let say show, for example, an animation where the info to be drawn homogeneously may be rendered/sent by the server really fast. We may play with that at this time on our local configs, but for drawing basic htm content remotely&#8230; I have to say that iframes are much easier/faster and cross-plateform to implement for the moment. Regarding the back-forward thing, I fully agree with Atli but something tells me that back-forwarding with anchor hashes, data cached in each iframes is really fast and enjoying on a navigation point of view so I would prefer to solve the headache with iframes or DOM based framework.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mario</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-258057</link>
		<dc:creator>mario</dc:creator>
		<pubDate>Thu, 01 Nov 2007 09:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-258057</guid>
		<description>Ajax has one weakness witch i find a great one, and i think that people working with it should consider it much more than they do t now...
Its problem with character encodings.
When you use Ajax call it does not render special charachter encodings other than utf-8.
Also when im borwsing some sites in spanish or some scandinavian languages ive noticed that browser does not render correctly some special characters ...(because i have set my browes to read char encodings form where im from)
Man that lets you with a bad test in your mouth..So we might say that A... sucks
Big idea(l)s often falls on small things!
...and we out!</description>
		<content:encoded><![CDATA[<p>Ajax has one weakness witch i find a great one, and i think that people working with it should consider it much more than they do t now&#8230;<br />
Its problem with character encodings.<br />
When you use Ajax call it does not render special charachter encodings other than utf-8.<br />
Also when im borwsing some sites in spanish or some scandinavian languages ive noticed that browser does not render correctly some special characters &#8230;(because i have set my browes to read char encodings form where im from)<br />
Man that lets you with a bad test in your mouth..So we might say that A&#8230; sucks<br />
Big idea(l)s often falls on small things!<br />
&#8230;and we out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matching</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-254989</link>
		<dc:creator>Matching</dc:creator>
		<pubDate>Wed, 05 Sep 2007 06:11:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-254989</guid>
		<description>Good! give user more experience.</description>
		<content:encoded><![CDATA[<p>Good! give user more experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: online backgammon</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-27671</link>
		<dc:creator>online backgammon</dc:creator>
		<pubDate>Thu, 15 Jun 2006 11:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-27671</guid>
		<description>Whatâ€™s the big deal about status? The only time I have needed any intermediate state other than â€œIâ€™m doneâ€ is when a request takes a long time and the Iframe method is actually much more poweful in that case becaue it can use progressive rendering of html.</description>
		<content:encoded><![CDATA[<p>Whatâ€™s the big deal about status? The only time I have needed any intermediate state other than â€œIâ€™m doneâ€ is when a request takes a long time and the Iframe method is actually much more poweful in that case becaue it can use progressive rendering of html.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: diatribe &#187; Blog Archive &#187; Of Interest v20060304.1</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-4234</link>
		<dc:creator>diatribe &#187; Blog Archive &#187; Of Interest v20060304.1</dc:creator>
		<pubDate>Sat, 04 Mar 2006 19:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-4234</guid>
		<description>[...] Compare, XHR v iFrame [...]</description>
		<content:encoded><![CDATA[<p>[...] Compare, XHR v iFrame [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shy Guy</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-4155</link>
		<dc:creator>Shy Guy</dc:creator>
		<pubDate>Thu, 02 Mar 2006 18:52:20 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-4155</guid>
		<description>I use XmlHttpRequest and feed response output to an iframe.</description>
		<content:encoded><![CDATA[<p>I use XmlHttpRequest and feed response output to an iframe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Gahl</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-4118</link>
		<dc:creator>Ryan Gahl</dc:creator>
		<pubDate>Wed, 01 Mar 2006 15:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-4118</guid>
		<description>Indeed, Atli. DOM script injection is (IMHO), the better of all 3 approaches. 

1. It requires no ActiveX
2. It&#039;s much faster than the XMLHTTPRequest object (I&#039;ve used both, done the tests). This is in regard to the actual construction of the object, and with regard to evaluating scripts (no clunky meniacal eval() calls).
3. Much smaller memory footprint.
4. Cross-site compatible.</description>
		<content:encoded><![CDATA[<p>Indeed, Atli. DOM script injection is (IMHO), the better of all 3 approaches. </p>
<p>1. It requires no ActiveX<br />
2. It&#8217;s much faster than the XMLHTTPRequest object (I&#8217;ve used both, done the tests). This is in regard to the actual construction of the object, and with regard to evaluating scripts (no clunky meniacal eval() calls).<br />
3. Much smaller memory footprint.<br />
4. Cross-site compatible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Atli Thorbjornsson</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-4109</link>
		<dc:creator>Atli Thorbjornsson</dc:creator>
		<pubDate>Wed, 01 Mar 2006 09:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-4109</guid>
		<description>I would have liked to see him address the third and much preferred (by me at least) method which is dynamic script inclusion. Simply adding a script object to the document is multithreaded and cross-site capable.

What&#039;s the big deal about status? The only time I have needed any intermediate state other than &quot;I&#039;m done&quot; is when a request takes a long time and the Iframe method is actually much more poweful in that case becaue it can use progressive rendering of html.

The back button is another headache altogether and is not really dependent on whether you use iframes or xmlhttprequest. If you want it to work your best bet is to implement a framework around it like the rsh object by Brad Neuberg or the related Hashlistener from Erik Arvidsen.</description>
		<content:encoded><![CDATA[<p>I would have liked to see him address the third and much preferred (by me at least) method which is dynamic script inclusion. Simply adding a script object to the document is multithreaded and cross-site capable.</p>
<p>What&#8217;s the big deal about status? The only time I have needed any intermediate state other than &#8220;I&#8217;m done&#8221; is when a request takes a long time and the Iframe method is actually much more poweful in that case becaue it can use progressive rendering of html.</p>
<p>The back button is another headache altogether and is not really dependent on whether you use iframes or xmlhttprequest. If you want it to work your best bet is to implement a framework around it like the rsh object by Brad Neuberg or the related Hashlistener from Erik Arvidsen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ahappylion</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-4108</link>
		<dc:creator>ahappylion</dc:creator>
		<pubDate>Wed, 01 Mar 2006 09:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-4108</guid>
		<description>it&#039;s easy,but very useful!!:)</description>
		<content:encoded><![CDATA[<p>it&#8217;s easy,but very useful!!:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Dill</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-4091</link>
		<dc:creator>Jeff Dill</dc:creator>
		<pubDate>Tue, 28 Feb 2006 21:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-4091</guid>
		<description>Another fundamental difference is that &lt;strong&gt;XMLHttpRequest requires ActiveX to be enabled in Internet Explorer&lt;/strong&gt;. This is a blocker for using XHR in many large deployments, especially b2b applications, where ActiveX is disabled for security reasons.
Of course, all of these differences can be papered over by a robust AJAX RIA framework, which automatically selects the best AJAX &#039;transport&#039;.</description>
		<content:encoded><![CDATA[<p>Another fundamental difference is that <strong>XMLHttpRequest requires ActiveX to be enabled in Internet Explorer</strong>. This is a blocker for using XHR in many large deployments, especially b2b applications, where ActiveX is disabled for security reasons.<br />
Of course, all of these differences can be papered over by a robust AJAX RIA framework, which automatically selects the best AJAX &#8216;transport&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CountZero</title>
		<link>http://ajaxian.com/archives/xmlhttprequest-vs-iframes/comment-page-1#comment-4090</link>
		<dc:creator>CountZero</dc:creator>
		<pubDate>Tue, 28 Feb 2006 20:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/xmlhttprequest-vs-iframes#comment-4090</guid>
		<description>well, actually nothing I didn&#039;t already know, but a real useful and comprehensive description of the differences for those who are not yet as adept with the backgrounds ;)</description>
		<content:encoded><![CDATA[<p>well, actually nothing I didn&#8217;t already know, but a real useful and comprehensive description of the differences for those who are not yet as adept with the backgrounds ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

