<?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: PHP: DOMDocument Performance</title>
	<atom:link href="http://www.duckwizard.com/2006/08/05/php-domdocument-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.duckwizard.com/2006/08/05/php-domdocument-performance/</link>
	<description></description>
	<pubDate>Sun, 23 Nov 2008 13:35:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: tacone</title>
		<link>http://www.duckwizard.com/2006/08/05/php-domdocument-performance/#comment-45</link>
		<dc:creator>tacone</dc:creator>
		<pubDate>Sat, 04 Nov 2006 03:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.duckwizard.com/2006/08/05/php-domdocument-performance/#comment-45</guid>
		<description>Hello. ( note: I am one of the hundreds which downloaded industry )
Why don't you cache compiled-dom-templates ? At basic level you could cache a string with php inserts (calling your custom functions) and just include the cached view. You only have to build 1:1 relationship beewten your custom tags and your functions.

Check out PEAR for caching routines ( saving cache, checking source freshness against stored cache and so on ).

For most pages, anyway, a good static cache (only for some page parts maybe ?) would be the faster  and simpler solution. Lot faster than php itself.

Beside that I don't consider a templating-engine to be necessary to achieve logic-content separation.

Cheers</description>
		<content:encoded><![CDATA[<p>Hello. ( note: I am one of the hundreds which downloaded industry )<br />
Why don&#8217;t you cache compiled-dom-templates ? At basic level you could cache a string with php inserts (calling your custom functions) and just include the cached view. You only have to build 1:1 relationship beewten your custom tags and your functions.</p>
<p>Check out PEAR for caching routines ( saving cache, checking source freshness against stored cache and so on ).</p>
<p>For most pages, anyway, a good static cache (only for some page parts maybe ?) would be the faster  and simpler solution. Lot faster than php itself.</p>
<p>Beside that I don&#8217;t consider a templating-engine to be necessary to achieve logic-content separation.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
