<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for astradele</title>
	<atom:link href="http://blog.astradele.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.astradele.com</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 17:16:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Getting Dell 1700 laser printer working on Ubuntu Linux by Nate in Phoenix, AZ, USA</title>
		<link>http://blog.astradele.com/2008/06/12/getting-dell-1700-laser-printer-working-on-ubuntu-linux/#comment-165</link>
		<dc:creator><![CDATA[Nate in Phoenix, AZ, USA]]></dc:creator>
		<pubDate>Fri, 03 Feb 2012 17:16:12 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/?p=6#comment-165</guid>
		<description><![CDATA[With my 1700n, and using Ubuntu 10.04LTS, I found that the standard, already loaded driver for the &#039;HP Laser Jet 1320&#039; works.. it IS the 1320, not the 1320n or other 1320(x) models.. select the first driver, called &#039;foomatic&#039; from that next menu, labelled:
&quot;HP Laser Jet 1320 Foomatic/pxlmono [en]&quot;
Super Spiffy... after trying almost every other DELL driver in the library and having my printer spit out 90 sheets of random characters to print a test page, having this work made my happy places happy once again  :D]]></description>
		<content:encoded><![CDATA[<p>With my 1700n, and using Ubuntu 10.04LTS, I found that the standard, already loaded driver for the &#8216;HP Laser Jet 1320&#8242; works.. it IS the 1320, not the 1320n or other 1320(x) models.. select the first driver, called &#8216;foomatic&#8217; from that next menu, labelled:<br />
&#8220;HP Laser Jet 1320 Foomatic/pxlmono [en]&#8221;<br />
Super Spiffy&#8230; after trying almost every other DELL driver in the library and having my printer spit out 90 sheets of random characters to print a test page, having this work made my happy places happy once again  <img src='http://s0.wp.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting pictures out of FlipAlbum by Raul</title>
		<link>http://blog.astradele.com/2005/10/21/getting-pictures-out-of-flipalbum/#comment-163</link>
		<dc:creator><![CDATA[Raul]]></dc:creator>
		<pubDate>Tue, 27 Dec 2011 04:49:41 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/?p=275#comment-163</guid>
		<description><![CDATA[Demo Builder 7 is the Solution!!]]></description>
		<content:encoded><![CDATA[<p>Demo Builder 7 is the Solution!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Slow XPath evaluation for large XML documents in Java 1.5 by Sunil</title>
		<link>http://blog.astradele.com/2006/02/24/slow-xpath-evaluation-for-large-xml-documents-in-java-15/#comment-162</link>
		<dc:creator><![CDATA[Sunil]]></dc:creator>
		<pubDate>Fri, 09 Dec 2011 17:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/?p=244#comment-162</guid>
		<description><![CDATA[Paul: Thanks for helping. I figured out my issue. I was not modifying the DOM anyways. I am just using XML as the layout. So, what I did was, just used cachedXpathApi class to process the Xpath queries and that got down my processing time from 10+ minutes for 1200 nodes to 30 seconds. I thinkk, it is better to go for CachedXpathApi when your DOM does not change because it caches the DOM and doesnt recreate DOM everytime and convet it into DTM. Thanks for the help.]]></description>
		<content:encoded><![CDATA[<p>Paul: Thanks for helping. I figured out my issue. I was not modifying the DOM anyways. I am just using XML as the layout. So, what I did was, just used cachedXpathApi class to process the Xpath queries and that got down my processing time from 10+ minutes for 1200 nodes to 30 seconds. I thinkk, it is better to go for CachedXpathApi when your DOM does not change because it caches the DOM and doesnt recreate DOM everytime and convet it into DTM. Thanks for the help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

