<?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: What a Thursday Night</title>
	<atom:link href="http://blog.joshuaeichorn.com/archives/2004/09/03/what-a-thursday-night/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.joshuaeichorn.com/archives/2004/09/03/what-a-thursday-night/</link>
	<description>The weblog of Joshua Eichorn, AJAX, PHP and Open Source</description>
	<pubDate>Wed, 07 Jan 2009 22:21:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: liz</title>
		<link>http://blog.joshuaeichorn.com/archives/2004/09/03/what-a-thursday-night/#comment-120</link>
		<dc:creator>liz</dc:creator>
		<pubDate>Thu, 16 Sep 2004 20:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joshuaeichorn.com/archives/2004/09/03/what-a-thursday-night/#comment-120</guid>
		<description>I believe xslt is cool too, I wish there were nifty CLIENT SIDE things to do transformations for you - but here's a really simplied version of the problem with using xslt...

In php you grab stuff from a db, file, whatever, put it in a template and display it...or you grab stuff from a db, format it to xml, apply xsl stylesheet transformation, and then display it.  See in essence you shove two extra steps in there - just like you shove extra steps in when you parse and compile templates :)</description>
		<content:encoded><![CDATA[<p>I believe xslt is cool too, I wish there were nifty CLIENT SIDE things to do transformations for you - but here&#8217;s a really simplied version of the problem with using xslt&#8230;</p>
<p>In php you grab stuff from a db, file, whatever, put it in a template and display it&#8230;or you grab stuff from a db, format it to xml, apply xsl stylesheet transformation, and then display it.  See in essence you shove two extra steps in there - just like you shove extra steps in when you parse and compile templates <img src='http://blog.joshuaeichorn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dinh</title>
		<link>http://blog.joshuaeichorn.com/archives/2004/09/03/what-a-thursday-night/#comment-107</link>
		<dc:creator>Dinh</dc:creator>
		<pubDate>Sun, 05 Sep 2004 10:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joshuaeichorn.com/archives/2004/09/03/what-a-thursday-night/#comment-107</guid>
		<description>XSLT is very cool. But I wonder if it could lead to some overhead in parsing XML files each time a PHP page loaded.</description>
		<content:encoded><![CDATA[<p>XSLT is very cool. But I wonder if it could lead to some overhead in parsing XML files each time a PHP page loaded.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manuzhai</title>
		<link>http://blog.joshuaeichorn.com/archives/2004/09/03/what-a-thursday-night/#comment-102</link>
		<dc:creator>Manuzhai</dc:creator>
		<pubDate>Sat, 04 Sep 2004 01:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joshuaeichorn.com/archives/2004/09/03/what-a-thursday-night/#comment-102</guid>
		<description>Why not just use XSLT? It's a W3C standard, quite powerful, quite nice.</description>
		<content:encoded><![CDATA[<p>Why not just use XSLT? It&#8217;s a W3C standard, quite powerful, quite nice.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
