<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Server-side FigureHandler thoughts</title>
	<link>http://www.easy-reader.net/archives/2007/10/11/server-side-figurehandler-thoughts/</link>
	<description>It&#8217;s a work in progress</description>
	<pubDate>Wed, 14 May 2008 00:36:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Faberlica</title>
		<link>http://www.easy-reader.net/archives/2007/10/11/server-side-figurehandler-thoughts/#comment-12222</link>
		<pubDate>Fri, 11 Jan 2008 08:23:59 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/10/11/server-side-figurehandler-thoughts/#comment-12222</guid>
					<description>Thankfully, most server-side languages support some means of DOM walking (albeit sometimes in less-than-desirable ways), but, as far as I know, none have a CSS parser, so you’d likely need to write that as well. From a server overhead point-of-view, I imagine that preprocessing would be fairly costly (most DOM-related stuff is), but the output for each page could be cached, reducing it somewhat.</description>
		<content:encoded><![CDATA[<p>Thankfully, most server-side languages support some means of <abbr title="Document Object Model">DOM</abbr> walking (albeit sometimes in less-than-desirable ways), but, as far as I know, none have a <abbr title="Cascading Style Sheets">CSS</abbr> parser, so you’d likely need to write that as well. From a server overhead point-of-view, I imagine that preprocessing would be fairly costly (most <abbr title="Document Object Model">DOM</abbr>-related stuff is), but the output for each page could be cached, reducing it somewhat.
</p>]]></content:encoded>
				</item>
</channel>
</rss>
