<?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"
	>
<channel>
	<title>Comments on: 2005: The year of the DOM</title>
	<atom:link href="http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Mon, 01 Dec 2008 20:11:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: arkitrave :: architecture, web design, and stuff &#187; CSS background images: content or presentation?</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-10289</link>
		<dc:creator>arkitrave :: architecture, web design, and stuff &#187; CSS background images: content or presentation?</dc:creator>
		<pubDate>Thu, 27 Oct 2005 23:30:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-10289</guid>
		<description>[...] From a philosophical, separation-of-content-presentation-behavior viewpoint, is the CSS background image a piece of content inside a style sheet, which should be presentation only? [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] From a philosophical, separation-of-content-presentation-behavior viewpoint, is the CSS background image a piece of content inside a style sheet, which should be presentation only? [&#8230;]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mmj</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3649</link>
		<dc:creator>mmj</dc:creator>
		<pubDate>Tue, 18 Jan 2005 10:23:54 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3649</guid>
		<description>&lt;p&gt;In a previous blog entry, a commenter asked why XMLHttpRequest was any better than using a hidden iframe (or script) element ashas been available for years, and I would like to reinterate this question.  XMLHttpRequest is a proprietary extension to JavaScript that was implemented first by Microsoft and is now available on recent Mozilla browsers (and some versions of Safari, I believe).  It is less well supported than the former methods, and it works slightly differently between Microsoft and Mozilla's implementation.  Its main benefit is the 'synchronous' mode, though I personally prefer the 'asynchonous' mode, as it does not stop the other behaviours of the page while something is loading.&lt;/p&gt;

&lt;p&gt;Is there any indication that XMLHttpRequest is here to stay, and is going to be included (in its present form) in any public standard?  It seems that the &lt;a href="http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/" rel="nofollow"&gt;level 3 DOM&lt;/a&gt; specification has chosen a different path with its Load and Save specification.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>In a previous blog entry, a commenter asked why XMLHttpRequest was any better than using a hidden iframe (or script) element ashas been available for years, and I would like to reinterate this question.  XMLHttpRequest is a proprietary extension to JavaScript that was implemented first by Microsoft and is now available on recent Mozilla browsers (and some versions of Safari, I believe).  It is less well supported than the former methods, and it works slightly differently between Microsoft and Mozilla&#8217;s implementation.  Its main benefit is the &#8217;synchronous&#8217; mode, though I personally prefer the &#8216;asynchonous&#8217; mode, as it does not stop the other behaviours of the page while something is loading.</p>
<p>Is there any indication that XMLHttpRequest is here to stay, and is going to be included (in its present form) in any public standard?  It seems that the <a href="http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/" rel="nofollow">level 3 DOM</a> specification has chosen a different path with its Load and Save specification.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: cejua</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3637</link>
		<dc:creator>cejua</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3637</guid>
		<description>&lt;p&gt;The XmlHttpRequest object has been available for some time now in IE and its great to see it's use in todays standards compliant browsers. &lt;/p&gt;

&lt;p&gt;As a sidenote - its interesting to see how ASP.NET 2.0 has the process of using XmlHttpRequest to quietly update a web page built in.&lt;/p&gt;

&lt;p&gt;If anyone is interested this article fully describes 'ASP.NET 2.0 Script Callbacks':&lt;/p&gt;

&lt;p&gt;http://msdn.microsoft.com/msdnmag/issues/04/08/CuttingEdge/&lt;/p&gt;

&lt;p&gt;&lt;br /&gt;
&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>The XmlHttpRequest object has been available for some time now in IE and its great to see it&#8217;s use in todays standards compliant browsers. </p>
<p>As a sidenote - its interesting to see how ASP.NET 2.0 has the process of using XmlHttpRequest to quietly update a web page built in.</p>
<p>If anyone is interested this article fully describes &#8216;ASP.NET 2.0 Script Callbacks&#8217;:</p>
<p><a href="http://msdn.microsoft.com/msdnmag/issues/04/08/CuttingEdge/" rel="nofollow">http://msdn.microsoft.com/msdnmag/issues/04/08/CuttingEdge/</a></p>
<p></p>]]></content:encoded>
	</item>
	<item>
		<title>By: vgarcia</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3638</link>
		<dc:creator>vgarcia</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3638</guid>
		<description>&lt;p&gt;I agree that we'll see cool uses of the DOM and XmlHttpRequest this year. I don't think accessibility will suffer too much when creating these scripts among those who care about it, but the real issue is getting those who didn't care about it in the first place to take notice and fix their scripts.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>I agree that we&#8217;ll see cool uses of the DOM and XmlHttpRequest this year. I don&#8217;t think accessibility will suffer too much when creating these scripts among those who care about it, but the real issue is getting those who didn&#8217;t care about it in the first place to take notice and fix their scripts.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Dante Evans</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3639</link>
		<dc:creator>Dante Evans</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3639</guid>
		<description>&lt;p&gt;There are 3 things that are going to be huge in 2005, and one of them is XMLHttpRequest (the other two are del.icio.us and WordPress). XMLHTTPRequest allows for interaction between del.icio.us and the client browser, and this is something I think we'll see a lot of this year. &lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>There are 3 things that are going to be huge in 2005, and one of them is XMLHttpRequest (the other two are del.icio.us and WordPress). XMLHTTPRequest allows for interaction between del.icio.us and the client browser, and this is something I think we&#8217;ll see a lot of this year. </p>]]></content:encoded>
	</item>
	<item>
		<title>By: WebCrawler</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3640</link>
		<dc:creator>WebCrawler</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3640</guid>
		<description>&lt;p&gt;I wonder, can we use serverside sessions with XMLHttpRequest ?&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>I wonder, can we use serverside sessions with XMLHttpRequest ?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Skunk</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3641</link>
		<dc:creator>Skunk</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3641</guid>
		<description>&lt;p&gt;If by servserside sessions you mean maintaining a session for a user then yes, absolutely - the content retrieved by XMLHttpRequest is usually dynamically generated on the server, and can hence be customised based on the user's cookie (or even a session identifier passed in the URL).&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>If by servserside sessions you mean maintaining a session for a user then yes, absolutely - the content retrieved by XMLHttpRequest is usually dynamically generated on the server, and can hence be customised based on the user&#8217;s cookie (or even a session identifier passed in the URL).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3642</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3642</guid>
		<description>&lt;p&gt;Look at this software http://www.innuvo.com/.  You can write all your code in Java which is complied into javascript.  It makes programming dynamic javascript much easier.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Look at this software <a href="http://www.innuvo.com/" rel="nofollow">http://www.innuvo.com/</a>.  You can write all your code in Java which is complied into javascript.  It makes programming dynamic javascript much easier.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Skunk</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3643</link>
		<dc:creator>Skunk</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3643</guid>
		<description>&lt;p&gt;Innuvo looks terrible: their main site doesn't even load in Safari (you get a blank page instead) and it appears to generate web applications that are completely useless if you don't have JavaScript - an accessibility nightmare! "Your browser currently has JavaScript disabled.  Please enable JavaScript to properly view this application." isn't the kind of dynamic web application future I'm looking forward to.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Innuvo looks terrible: their main site doesn&#8217;t even load in Safari (you get a blank page instead) and it appears to generate web applications that are completely useless if you don&#8217;t have JavaScript - an accessibility nightmare! &#8220;Your browser currently has JavaScript disabled.  Please enable JavaScript to properly view this application.&#8221; isn&#8217;t the kind of dynamic web application future I&#8217;m looking forward to.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: ant1832</title>
		<link>http://www.sitepoint.com/blogs/2005/01/05/2005-the-year-of-the-dom/#comment-3644</link>
		<dc:creator>ant1832</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1692762611#comment-3644</guid>
		<description>&lt;p&gt;I've been using xmlhttprequest in all of my latest projects.  I have to agree that this is going to be really hot in 05.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using xmlhttprequest in all of my latest projects.  I have to agree that this is going to be really hot in 05.</p>]]></content:encoded>
	</item>
</channel>
</rss>
