<?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: Faster DOM Queries</title>
	<atom:link href="http://ajaxian.com/archives/faster-dom-queries/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/faster-dom-queries</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: Jason Haley</title>
		<link>http://ajaxian.com/archives/faster-dom-queries/comment-page-1#comment-6558</link>
		<dc:creator>Jason Haley</dc:creator>
		<pubDate>Tue, 11 Apr 2006 11:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/faster-dom-queries#comment-6558</guid>
		<description>&lt;strong&gt;Interesting Finds&lt;/strong&gt;

</description>
		<content:encoded><![CDATA[<p><strong>Interesting Finds</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Clay</title>
		<link>http://ajaxian.com/archives/faster-dom-queries/comment-page-1#comment-6537</link>
		<dc:creator>Stephen Clay</dc:creator>
		<pubDate>Tue, 11 Apr 2006 03:09:19 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/faster-dom-queries#comment-6537</guid>
		<description>I guess I don&#039;t understand the big need for speed in this dept. Seems like if you have to do huge DOM queries on every page, maybe the app could use a redesign/optimization in general. XPath looks good, but you could also just have your server-side code spit out an array of IDs in a script element and loop over that with getElementById. Basically move the hassle of finding certain DOM elements onto the server&#039;s shoulders where you&#039;ve got plenty of speed.</description>
		<content:encoded><![CDATA[<p>I guess I don&#8217;t understand the big need for speed in this dept. Seems like if you have to do huge DOM queries on every page, maybe the app could use a redesign/optimization in general. XPath looks good, but you could also just have your server-side code spit out an array of IDs in a script element and loop over that with getElementById. Basically move the hassle of finding certain DOM elements onto the server&#8217;s shoulders where you&#8217;ve got plenty of speed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pavan Keely</title>
		<link>http://ajaxian.com/archives/faster-dom-queries/comment-page-1#comment-6482</link>
		<dc:creator>Pavan Keely</dc:creator>
		<pubDate>Mon, 10 Apr 2006 20:25:50 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/faster-dom-queries#comment-6482</guid>
		<description>Hi all,

I really don&#039;t think doing that (Alex&#039;s) hack will make accessing elements with same id faster. The faster way is to use document.all. Most of the browsers implemented &lt;b&gt;document.all&lt;/b&gt; now. Please check the fastness by yourself with the following link:
http://www.geocities.com/keelypavan/DOMFasterMethods.html .
Please click on the second button first as Alex&#039;s method is resetting ids. I tested in IE 6, Firefox 1.5, opera 8.54 and in all these browsers document.all method took almost 0ms. I know it&#039;s not a W3C standard but when all the browsers implemented that, I don;t see any other reason why we should stop using that.

Pavan Keely</description>
		<content:encoded><![CDATA[<p>Hi all,</p>
<p>I really don&#8217;t think doing that (Alex&#8217;s) hack will make accessing elements with same id faster. The faster way is to use document.all. Most of the browsers implemented <b>document.all</b> now. Please check the fastness by yourself with the following link:<br />
<a href="http://www.geocities.com/keelypavan/DOMFasterMethods.html" rel="nofollow">http://www.geocities.com/keelypavan/DOMFasterMethods.html</a> .<br />
Please click on the second button first as Alex&#8217;s method is resetting ids. I tested in IE 6, Firefox 1.5, opera 8.54 and in all these browsers document.all method took almost 0ms. I know it&#8217;s not a W3C standard but when all the browsers implemented that, I don;t see any other reason why we should stop using that.</p>
<p>Pavan Keely</p>
]]></content:encoded>
	</item>
</channel>
</rss>

