[Uw-ruby] DOM or Stream parsing?

[Dan McHarness]

FWIW, using the REXML::StreamListener I got the
following results:

via Benchmark test ~9.5 sec (avg of 3 tests)
via unit test: ~11.25 sec (avg of 3 tests)

--- Dan McHarness <dmcharness at yahoo.com> wrote:

> FWIW my view is that for this introductory class I
> should be learning how to use the standard XML
> library
> that ships with ruby. Saying that, I'll be looking
> to
> use the SAX approach over DOM if I can, but I want
> to
> make sure I first understand how to utilize REXML.
> 
> 
> 
> 
> --- uw-ruby-request at zenspider.com wrote:
> 
> > Send Uw-ruby mailing list submissions to
> > 	uw-ruby at zenspider.com
> > 
> > To subscribe or unsubscribe via the World Wide
> Web,
> > visit
> > 	http://www.zenspider.com/mailman/listinfo/uw-ruby
> > or, via email, send a message with subject or body
> > 'help' to
> > 	uw-ruby-request at zenspider.com
> > 
> > You can reach the person managing the list at
> > 	uw-ruby-owner at zenspider.com
> > 
> > When replying, please edit your Subject line so it
> > is more specific
> > than "Re: Contents of Uw-ruby digest..."
> > 
> > 
> > Today's Topics:
> > 
> >    1. DOM or Stream parsing? (Garrick West)
> >    2. Re: DOM or Stream parsing? (Richard Leickly)
> >    3. Re: DOM or Stream parsing? (Mark Holton)
> > 
> > 
> >
>
----------------------------------------------------------------------
> > 
> > Message: 1
> > Date: Sat, 17 Nov 2007 23:44:43 -0800
> > From: "Garrick West" <garrick at acm.org>
> > Subject: [Uw-ruby] DOM or Stream parsing?
> > To: Uw-ruby at zenspider.com
> > Message-ID:
> > 
> >
>
<9e0ec7f70711172344k5ece4150x48027f44ca531dc6 at mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> > 
> > Hi Ryan,
> > I figured I'd send this to the list as others
> might
> > be interested in your
> > response:
> > 
> > Wow.  That iTunes library is a bit of a monster to
> > pull in with DOM, but it
> > seems to work (at least on my system;).  The DTD
> is
> > almost as simple as you
> > can get, so it's not it would be too hard to do
> > Stream parsing, but I
> > question the value of doing so If you're not
> > concerned about the load time.
> >  It takes 54 seconds on my 2nd gen MacBook Pro
> > usingREXML, and I've seen
> > some form posts googling around suggesting libxml
> is
> > faster,
> > but can be a pain to set up (possibly dated?).
> > 
> > Thoughts?
> > --Garrick West
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
> >
>
http://www.zenspider.com/pipermail/uw-ruby/attachments/20071117/639146b6/attachment-0001.html
> > 
> > ------------------------------
> > 
> > Message: 2
> > Date: Sun, 18 Nov 2007 00:39:36 -0800
> > From: "Richard Leickly"
> > <Richard at iphc.washington.edu>
> > Subject: Re: [Uw-ruby] DOM or Stream parsing?
> > To: "UW's Ruby Certificate Program"
> > <uw-ruby at zenspider.com>
> > Message-ID:
> > 
> >
>
<40F0CA56251F1445A08B6019E34798B175BB61 at everglade.iphc.washington.edu>
> > Content-Type: text/plain; charset="us-ascii"
> > 
> > I don't know all those acronyms; but it sounds
> like
> > you are rolling in
> > some heavy artillary, Garrick !!
> > I used file.open() on the xml file.  Quick. The
> > greps and the operations
> > on the resulting arrays were also quick. I have a
> v.
> > old Dell Platitude
> > laptop. 
> >  
> > RD: maybe we could look at some of the more
> > interesting solutions in
> > class.  Sounds like GW has more tricks than Felix
> > The Cat.
> >  
> > Richard Leickly
> >  
> > P.S. Yes...I am working on the weekend. Yes..I do
> > have a life.
> > ________________________________
> > 
> > From: uw-ruby-bounces at zenspider.com
> > [mailto:uw-ruby-bounces at zenspider.com] On Behalf
> Of
> > Garrick West
> > Sent: Saturday, November 17, 2007 11:45 PM
> > To: Uw-ruby at zenspider.com
> > Subject: [Uw-ruby] DOM or Stream parsing?
> > 
> > 
> > Hi Ryan,
> > I figured I'd send this to the list as others
> might
> > be interested in
> > your response:
> > 
> > Wow.  That iTunes library is a bit of a monster to
> > pull in with DOM, but
> > it seems to work (at least on my system;).  The
> DTD
> > is almost as simple
> > as you can get, so it's not it would be too hard
> to
> > do Stream parsing,
> > but I question the value of doing so If you're not
> > concerned about the
> > load time.  It takes 54 seconds on my 2nd gen
> > MacBook Pro using 
> > REXML, and I've seen some form posts googling
> around
> > suggesting libxml
> > is faster,
> > but can be a pain to set up (possibly dated?).
> > 
> > 
> > Thoughts?
> > --Garrick West
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
> >
>
http://www.zenspider.com/pipermail/uw-ruby/attachments/20071118/0fa1c186/attachment-0001.html
> > 
> > ------------------------------
> > 
> > Message: 3
> > Date: Sun, 18 Nov 2007 01:45:20 -0800
> > From: "Mark Holton" <holtonma at gmail.com>
> > Subject: Re: [Uw-ruby] DOM or Stream parsing?
> > To: "UW's Ruby Certificate Program"
> > <uw-ruby at zenspider.com>
> > Message-ID:
> > 
> >
>
<8bd9e8730711180145g4802903eie1f30e8aefa55d37 at mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> > 
> > Came across this tonight: XmlSimple library ...in
> > the 'xml-simple' gem...
> > parses an XML document into a Ruby hash.
> > 
> > Guessing, and from what I read, there are no
> > performance saving when sucking
> > in the XML, but the resulting object is easier to
> > use -- ends up as nested
> > structure of Ruby hashes and arrays.
> > 
> > http://xml-simple.rubyforge.org/
> > 
> > :Holton
> > 
> > 
> > On Nov 17, 2007 11:44 PM, Garrick West
> > <garrick at acm.org> wrote:
> > 
> > > Hi Ryan,
> > > I figured I'd send this to the list as others
> > might be interested in your
> > > response:
> > >
> > > Wow.  That iTunes library is a bit of a monster
> to
> 
=== message truncated ===



      ____________________________________________________________________________________
Be a better sports nut!  Let your teams follow you 
with Yahoo Mobile. Try it now.  http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ