<?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/"
	>
<channel>
	<title>Comments on: Hpricot - My New Favourite Ruby XML Parser</title>
	<atom:link href="http://www.peterkrantz.com/2007/ruby-xml-parsing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterkrantz.com/2007/ruby-xml-parsing/</link>
	<description>A blog about technology, visualization, music and unmanned vehicle experiments</description>
	<pubDate>Tue, 06 Jan 2009 22:02:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Fear and Loathing in Software Development &#124; Educate. Liberate.</title>
		<link>http://www.peterkrantz.com/2007/ruby-xml-parsing/comment-page-1/#comment-2046</link>
		<dc:creator>Fear and Loathing in Software Development &#124; Educate. Liberate.</dc:creator>
		<pubDate>Sat, 29 Sep 2007 22:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkrantz.com/2007/ruby-xml-parsing/#comment-2046</guid>
		<description>[...] project I&#8217;ve worked on since it was initially released. This can further be evidenced by various people around the net, and several personal [...]</description>
		<content:encoded><![CDATA[<p>[...] project I&#8217;ve worked on since it was initially released. This can further be evidenced by various people around the net, and several personal [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.peterkrantz.com/2007/ruby-xml-parsing/comment-page-1/#comment-1985</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 27 Jul 2007 23:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkrantz.com/2007/ruby-xml-parsing/#comment-1985</guid>
		<description>Thank you so much for making this comment on the web. I also found REXML to be very slow and libxml is super hard to install on windows - at least i couldn't get it to run after hours of work and finally decided to look for other XML implementations. 
Hpricot installed out of the box with gem and I successfully replaced all REXML commands with hpricot API without any problems. The XML process time improved from 30 seconds to 1. Thanks!</description>
		<content:encoded><![CDATA[<p>Thank you so much for making this comment on the web. I also found REXML to be very slow and libxml is super hard to install on windows - at least i couldn&#8217;t get it to run after hours of work and finally decided to look for other XML implementations.<br />
Hpricot installed out of the box with gem and I successfully replaced all REXML commands with hpricot API without any problems. The XML process time improved from 30 seconds to 1. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Borenstein</title>
		<link>http://www.peterkrantz.com/2007/ruby-xml-parsing/comment-page-1/#comment-1965</link>
		<dc:creator>Greg Borenstein</dc:creator>
		<pubDate>Mon, 11 Jun 2007 18:39:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkrantz.com/2007/ruby-xml-parsing/#comment-1965</guid>
		<description>Just today, I experienced the same problem as Hedley with Hpricot's XPath and CSS selectors failing to navigate a namespaced xml doc. With a little bit of hunting around in the wiki, I discovered that the problem seems to have been fixed in a recent change:

http://code.whytheluckystiff.net/hpricot/changeset/146

Upgrading my gem to 0.5 got things working for me. I can now navigate namespaced xml docs as normal with Hpricot. The one tangle seems to be that Hpricot still downcases all of the tags, so I had to take that into account when constructing my selectors. There's some discussion of the problem over on the wiki so it is somewhat likely on its way towards resolution.</description>
		<content:encoded><![CDATA[<p>Just today, I experienced the same problem as Hedley with Hpricot&#8217;s XPath and CSS selectors failing to navigate a namespaced xml doc. With a little bit of hunting around in the wiki, I discovered that the problem seems to have been fixed in a recent change:</p>
<p><a href="http://code.whytheluckystiff.net/hpricot/changeset/146" rel="nofollow">http://code.whytheluckystiff.net/hpricot/changeset/146</a></p>
<p>Upgrading my gem to 0.5 got things working for me. I can now navigate namespaced xml docs as normal with Hpricot. The one tangle seems to be that Hpricot still downcases all of the tags, so I had to take that into account when constructing my selectors. There&#8217;s some discussion of the problem over on the wiki so it is somewhat likely on its way towards resolution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hedley Robertson</title>
		<link>http://www.peterkrantz.com/2007/ruby-xml-parsing/comment-page-1/#comment-1920</link>
		<dc:creator>Hedley Robertson</dc:creator>
		<pubDate>Fri, 30 Mar 2007 21:06:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkrantz.com/2007/ruby-xml-parsing/#comment-1920</guid>
		<description>One thing I found is that hpricot does not like namespaces in the xml, so to be able to parse them I just substituted the ':' away, then it could read the tags again.

sms:  Documentation for hpricot is here: http://code.whytheluckystiff.net/hpricot/wiki/AnHpricotShowcase</description>
		<content:encoded><![CDATA[<p>One thing I found is that hpricot does not like namespaces in the xml, so to be able to parse them I just substituted the &#8216;:&#8217; away, then it could read the tags again.</p>
<p>sms:  Documentation for hpricot is here: <a href="http://code.whytheluckystiff.net/hpricot/wiki/AnHpricotShowcase" rel="nofollow">http://code.whytheluckystiff.net/hpricot/wiki/AnHpricotShowcase</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sms</title>
		<link>http://www.peterkrantz.com/2007/ruby-xml-parsing/comment-page-1/#comment-1692</link>
		<dc:creator>sms</dc:creator>
		<pubDate>Mon, 05 Mar 2007 06:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkrantz.com/2007/ruby-xml-parsing/#comment-1692</guid>
		<description>Hi ..
Can you post a link to the reference for Hpricot.
As with everything in Ruby the documentation is hard .. very hard to find.
The link by mechanized on rubyforge is dead .. has been that way for a few days.

Thanks</description>
		<content:encoded><![CDATA[<p>Hi ..<br />
Can you post a link to the reference for Hpricot.<br />
As with everything in Ruby the documentation is hard .. very hard to find.<br />
The link by mechanized on rubyforge is dead .. has been that way for a few days.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Hutchison</title>
		<link>http://www.peterkrantz.com/2007/ruby-xml-parsing/comment-page-1/#comment-1602</link>
		<dc:creator>Brian Hutchison</dc:creator>
		<pubDate>Thu, 22 Feb 2007 23:45:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkrantz.com/2007/ruby-xml-parsing/#comment-1602</guid>
		<description>Thanks for the posting! 

eI also had the same problem with REXML and found a Windows binary that someone had blogged about making. My question for you is, how would you compare the performance of Hpricot vs. libxml?  My app is particularly sensitive to speed, so although Hpricot might be easier I am wondering what you saw performance wise?  One file I have that I would like to parse is 20megs!  I might have to pre-process it first, but still - some larger data sets.

I also pull in an XML web service and one page was taking 15-20 seconds using REXML and it dropped to about 1.5 seconds using libxml, and most of that is in waiting for the external web service.</description>
		<content:encoded><![CDATA[<p>Thanks for the posting! </p>
<p>eI also had the same problem with REXML and found a Windows binary that someone had blogged about making. My question for you is, how would you compare the performance of Hpricot vs. libxml?  My app is particularly sensitive to speed, so although Hpricot might be easier I am wondering what you saw performance wise?  One file I have that I would like to parse is 20megs!  I might have to pre-process it first, but still - some larger data sets.</p>
<p>I also pull in an XML web service and one page was taking 15-20 seconds using REXML and it dropped to about 1.5 seconds using libxml, and most of that is in waiting for the external web service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MikeBlake</title>
		<link>http://www.peterkrantz.com/2007/ruby-xml-parsing/comment-page-1/#comment-1461</link>
		<dc:creator>MikeBlake</dc:creator>
		<pubDate>Wed, 14 Feb 2007 21:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkrantz.com/2007/ruby-xml-parsing/#comment-1461</guid>
		<description>Hi Peter,

I had the same prblem with REXML, will check out Hpricot... Good to see you hacking away on Leave!</description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>I had the same prblem with REXML, will check out Hpricot&#8230; Good to see you hacking away on Leave!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
