<?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: 4 Layers of&#160;Separation</title>
	<atom:link href="http://particletree.com/features/4-layers-of-separation/feed/" rel="self" type="application/rss+xml" />
	<link>http://particletree.com/features/4-layers-of-separation/</link>
	<description>Everyone needs a hug.</description>
	<pubDate>Wed, 19 Nov 2008 11:48:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Hillari</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-20311</link>
		<dc:creator>Hillari</dc:creator>
		<pubDate>Tue, 13 Mar 2007 23:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-20311</guid>
		<description>&lt;p&gt;Cool!.. Nice work...i&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Cool!.. Nice work&#8230;i</p>]]></content:encoded>
	</item>
	<item>
		<title>By: hwwyppcktl</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-14732</link>
		<dc:creator>hwwyppcktl</dc:creator>
		<pubDate>Thu, 01 Feb 2007 18:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-14732</guid>
		<description>&lt;p&gt;http://prlncdqkrym.com&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><a href="http://prlncdqkrym.com" rel="nofollow">http://prlncdqkrym.com</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: YSuoryNNS5</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-10071</link>
		<dc:creator>YSuoryNNS5</dc:creator>
		<pubDate>Fri, 12 Jan 2007 03:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-10071</guid>
		<description>&lt;p&gt;Hi! Very nice site! Thanks you very much! lgcNbxQGbU&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi! Very nice site! Thanks you very much! lgcNbxQGbU</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Hillari</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-4961</link>
		<dc:creator>Hillari</dc:creator>
		<pubDate>Tue, 12 Dec 2006 20:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-4961</guid>
		<description>&lt;p&gt;Great site. I will bookmark for my sons to view as well!!!i&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great site. I will bookmark for my sons to view as well!!!i</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Campbell</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-1077</link>
		<dc:creator>Ryan Campbell</dc:creator>
		<pubDate>Mon, 30 Jan 2006 22:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-1077</guid>
		<description>&lt;p&gt;Tyler - once you have an XML file, XSL can parse it quickly. In my workings with this technique, I have found a couple performance problems:&lt;/p&gt;

&lt;p&gt;1) PHP pulls from the database and the writes the results in XML format. XSL parses the XML, and echos the response to the client. The clients Ajax request then places the result in the DOM. This part went faster just embedding markup into the PHP and echoing it out, but the separation was lost.&lt;/p&gt;

&lt;p&gt;2) Client side XSL processors were much faster than server side. If the application does not need to be degradable, then I would go this way because the performance was great.&lt;/p&gt;

&lt;p&gt;It is good to hear XSL being used ni large projects and keeping up performance and stability. I am a fan of the technology, and would like to keep using it more.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Tyler - once you have an XML file, XSL can parse it quickly. In my workings with this technique, I have found a couple performance problems:</p>

<p>1) PHP pulls from the database and the writes the results in XML format. XSL parses the XML, and echos the response to the client. The clients Ajax request then places the result in the DOM. This part went faster just embedding markup into the PHP and echoing it out, but the separation was lost.</p>

<p>2) Client side XSL processors were much faster than server side. If the application does not need to be degradable, then I would go this way because the performance was great.</p>

<p>It is good to hear XSL being used ni large projects and keeping up performance and stability. I am a fan of the technology, and would like to keep using it more.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler McMullen</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-1076</link>
		<dc:creator>Tyler McMullen</dc:creator>
		<pubDate>Mon, 30 Jan 2006 09:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-1076</guid>
		<description>&lt;p&gt;Excellent article.  I just disagree on one point... well... not necessarily disagree but...
XSLT is actually quite fast.  I worked on a project a few years ago (you know... before AJAX was called AJAX :P) which used xmlhttprequests and xslt's for display.  One of our reports had to parse through something like 10,000 records in one shot.  We assumed that it would be faster to do it simply in Javascript.  Wrong.  The XSLT parsed it in less than 3 seconds, whereas the Javascript took something like 15.&lt;/p&gt;

&lt;p&gt;The details are kind of funny as this was about 3 years ago, but anyway my point is that for large data transformations... XSLT is amazingly fast.&lt;/p&gt;

&lt;p&gt;XSLT is just amazing in general.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Excellent article.  I just disagree on one point&#8230; well&#8230; not necessarily disagree but&#8230;
XSLT is actually quite fast.  I worked on a project a few years ago (you know&#8230; before AJAX was called AJAX :P) which used xmlhttprequests and xslt&#8217;s for display.  One of our reports had to parse through something like 10,000 records in one shot.  We assumed that it would be faster to do it simply in Javascript.  Wrong.  The XSLT parsed it in less than 3 seconds, whereas the Javascript took something like 15.</p>

<p>The details are kind of funny as this was about 3 years ago, but anyway my point is that for large data transformations&#8230; XSLT is amazingly fast.</p>

<p>XSLT is just amazing in general.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler McMullen</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-1075</link>
		<dc:creator>Tyler McMullen</dc:creator>
		<pubDate>Mon, 30 Jan 2006 09:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-1075</guid>
		<description>&lt;p&gt;Excellent article.  I just disagree on one point... well... not necessarily disagree but...
XSLT is actually quite fast.  I worked on a project a few years ago (you know... before AJAX was called AJAX :P) which used xmlhttprequests and xslt's for display.  One of our reports had to parse through something like 10,000 records in one shot.  We assumed that it would be faster to do it simply in Javascript.  Wrong.  The XSLT parsed it in less than 3 seconds, whereas the Javascript took something like 15.&lt;/p&gt;

&lt;p&gt;The details are kind of funny as this was about 3 years ago, but anyway my point is that for large data transformations... XSLT is amazingly fast.&lt;/p&gt;

&lt;p&gt;XSLT is just amazing in general.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Excellent article.  I just disagree on one point&#8230; well&#8230; not necessarily disagree but&#8230;
XSLT is actually quite fast.  I worked on a project a few years ago (you know&#8230; before AJAX was called AJAX :P) which used xmlhttprequests and xslt&#8217;s for display.  One of our reports had to parse through something like 10,000 records in one shot.  We assumed that it would be faster to do it simply in Javascript.  Wrong.  The XSLT parsed it in less than 3 seconds, whereas the Javascript took something like 15.</p>

<p>The details are kind of funny as this was about 3 years ago, but anyway my point is that for large data transformations&#8230; XSLT is amazingly fast.</p>

<p>XSLT is just amazing in general.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Alessandro</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-1074</link>
		<dc:creator>Alessandro</dc:creator>
		<pubDate>Sat, 12 Nov 2005 13:01:46 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-1074</guid>
		<description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;I tried your Todo List Demo in FF 1.0.7 but, with or without javascript, it show this kind of errors:&lt;/p&gt;

&lt;p&gt;Warning: mysql_connect() [function.mysql-connect]: Access denied for user 'particle_web'@'particletree.com' (using password: YES) in /home/httpd/vhosts/particletree.com/httpdocs/examples/degradableajax/cDatabase.php on line 93&lt;/p&gt;

&lt;p&gt;What's the matter?&lt;/p&gt;

&lt;p&gt;Great article.&lt;/p&gt;

&lt;p&gt;Ale&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi,</p>

<p>I tried your Todo List Demo in FF 1.0.7 but, with or without javascript, it show this kind of errors:</p>

<p>Warning: mysql_connect() [function.mysql-connect]: Access denied for user &#8216;particle_web&#8217;@&#8217;particletree.com&#8217; (using password: YES) in /home/httpd/vhosts/particletree.com/httpdocs/examples/degradableajax/cDatabase.php on line 93</p>

<p>What&#8217;s the matter?</p>

<p>Great article.</p>

<p>Ale</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-1073</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Thu, 10 Nov 2005 08:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-1073</guid>
		<description>&lt;p&gt;Great article. The layer ideas are great . I liked the part that said that XSL is tough going. I have seen some XSLT generating java script, people need some direction out there! I have been programming for 15 yrs, and I must say it was the most difficult language to learn (I call XSLT the end users revenge on programmers! finally they have a language to confuse us! Interesting how different mind sets think.&lt;/p&gt;

&lt;p&gt;Anyway great article.&lt;/p&gt;

&lt;p&gt;mike&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great article. The layer ideas are great . I liked the part that said that XSL is tough going. I have seen some XSLT generating java script, people need some direction out there! I have been programming for 15 yrs, and I must say it was the most difficult language to learn (I call XSLT the end users revenge on programmers! finally they have a language to confuse us! Interesting how different mind sets think.</p>

<p>Anyway great article.</p>

<p>mike</p>]]></content:encoded>
	</item>
	<item>
		<title>By: david gee</title>
		<link>http://particletree.com/features/4-layers-of-separation/#comment-1072</link>
		<dc:creator>david gee</dc:creator>
		<pubDate>Tue, 08 Nov 2005 21:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://s2462.gridserver.com/wordpress/?p=141#comment-1072</guid>
		<description>&lt;p&gt;Thanks for the great article. I've been using XSLT for financial business apps since about 2000. There is definitely a conception amongst back-end developers that it's a very tough language to learn, but coming from a front-end XHTML/CSS background I found it very straightforward, with none of the hiccups, quirks and blatant oversights of CSS. The basic hurdle is getting over the recursive nature of the language, once you grasp that it becomes very easy.&lt;/p&gt;

&lt;p&gt;I find using XML/XSLT a very handy tool for rapid iterative prototyping, as you can set up an underlying data structure once and build multiple modular views. Using client-side XSLT transformations, it's possible to build up a fully-functional &#38; portable prototype for things like demos and usability testing, with no need for an attached database.&lt;/p&gt;

&lt;p&gt;A few things:&lt;/p&gt;

&lt;p&gt;In your article, you mention that ASP.Net "code-behind" pages need to be compiled. This is no longer true with .Net 2.0, which is a great step forward.&lt;/p&gt;

&lt;p&gt;For those learning XSLT for the first time, I &lt;em&gt;highly&lt;/em&gt; recommend the Microsoft MSXML 4.0 SDK help files. They are very thorough, very well written, and as far as I recall, all the proprietary MS functions are broken out into a seperate section. This is what I first used when starting out with XML, and I was up and running in a few days.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for the great article. I&#8217;ve been using XSLT for financial business apps since about 2000. There is definitely a conception amongst back-end developers that it&#8217;s a very tough language to learn, but coming from a front-end XHTML/CSS background I found it very straightforward, with none of the hiccups, quirks and blatant oversights of CSS. The basic hurdle is getting over the recursive nature of the language, once you grasp that it becomes very easy.</p>

<p>I find using XML/XSLT a very handy tool for rapid iterative prototyping, as you can set up an underlying data structure once and build multiple modular views. Using client-side XSLT transformations, it&#8217;s possible to build up a fully-functional &amp; portable prototype for things like demos and usability testing, with no need for an attached database.</p>

<p>A few things:</p>

<p>In your article, you mention that ASP.Net &#8220;code-behind&#8221; pages need to be compiled. This is no longer true with .Net 2.0, which is a great step forward.</p>

<p>For those learning XSLT for the first time, I <em>highly</em> recommend the Microsoft MSXML 4.0 SDK help files. They are very thorough, very well written, and as far as I recall, all the proprietary MS functions are broken out into a seperate section. This is what I first used when starting out with XML, and I was up and running in a few days.</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.241 seconds -->
