[jdom-interest] streamdom -- middle ground between SAX and DO M

[Vijay Kumar]

Does this mean that the document will be parsed by the Sax parser everytime 
we need to look up a node in the document. I don;t see any other way of
getting an 
arbiterary node from a SAX based parser. 

If you have to parse it everytime from the start it could be really be
inefficient 
(time wise) for large XML doc, and if we can;t use it for large docs then
might as well
use DOM.

Am I missing some thing?

Vijay





Message: 6
From: V Lakshman <lak at vlakshman.com>
Organization: Artificial Intelligence Software
To: jdom-interest at jdom.org
Date: Mon, 31 Dec 2001 10:36:26 -0600
Subject: [jdom-interest] streamdom -- middle ground between SAX and DOM

I know most of us hate SAX, but what we don't like
about SAX is the "low-level" of it.  We would prefer
DOM, but how can we use DOM on large documents
or streaming data?

Well, one way is to have programmers
process SAX-like events, except that the event-handling
callbacks get to process entire elements (complete with
children and attributes, although of-course, no siblings).

I've written such a package (it's really just one class) --
called streamdom:
   http://streamdom.sourceforge.net/    or
   https://sourceforge.net/projects/streamdom/
It is currently built on a SAX2 parser and a DOM builder.
The Java API doc is here:
  http://streamdom.sourceforge.net/java/api/index.html

Is there interest in a JDOM version that would
go in jdom-contrib?  If there is, I could commit it in.

thanks
lakshman

--__--__--

Message: 7
Reply-To: "Brian Wolf" <brianw at knowledgextensions.com>
From: "Brian Wolf" <brianw at knowledgextensions.com>
To: "V Lakshman" <lak at vlakshman.com>, <jdom-interest at jdom.org>
Cc: "Dave Geoghegan" <daveg at knowledgextensions.com>
Subject: Re: [jdom-interest] streamdom -- middle ground between SAX and DOM
Date: Mon, 31 Dec 2001 10:12:37 -0500

This is a wonderful idea, and if I may suggest
further elaboration, it would be nice to have JDOM
supply a single API, SAX or DOM
invisible to the programmer, but are real-time,
and dynamic decisions made by the parser behind the scenes,
based on system monitoring and resource optimization  scheme

-Brian

----- Original Message -----
From: V Lakshman <lak at vlakshman.com>
To: <jdom-interest at jdom.org>
Sent: Monday, December 31, 2001 11:36 AM
Subject: [jdom-interest] streamdom -- middle ground between SAX and DOM


> I know most of us hate SAX, but what we don't like
> about SAX is the "low-level" of it.  We would prefer
> DOM, but how can we use DOM on large documents
> or streaming data?
>
> Well, one way is to have programmers
> process SAX-like events, except that the event-handling
> callbacks get to process entire elements (complete with
> children and attributes, although of-course, no siblings).
>
> I've written such a package (it's really just one class) --
> called streamdom:
>    http://streamdom.sourceforge.net/    or
>    https://sourceforge.net/projects/streamdom/
> It is currently built on a SAX2 parser and a DOM builder.
> The Java API doc is here:
>   http://streamdom.sourceforge.net/java/api/index.html
>
> Is there interest in a JDOM version that would
> go in jdom-contrib?  If there is, I could commit it in.
>
> thanks
> lakshman
> _______________________________________________
> To control your jdom-interest membership:
>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
>
>



--__--__--

_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com

End of jdom-interest Digest