cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierpaolo Fumagalli <>
Subject Re: [Moving on] SAX vs. DOM part II
Date Mon, 24 Jan 2000 18:51:11 GMT
Paul Russell wrote:
> > As you say, complex processors might end up building a DOM from the SAX
> > input, 'cos it's easier to deal with.  The worst case scenario is when two
> > processors that use DOM internally are stacked together: the first ends up
> > unwinding it's output DOM into SAX events, which the second uses to
> > re-create a DOM.  I wonder how much overhead there actually is in doing
> > this ... it's not going to be any worse than "Node.cloneNode(true)", is it?
> Wouldn't it make sense to create an 'adapter' that sits between each set of
> nodes and translates between the two models on an as needed basis - that
> way, only required translations would actually happen. Just a thought.

An AbstractDOMFilter... Yep... I am writing right now the SaxToDom and
DomToSax utilities, that can be used in those cases.


-          P              I              E              R          -
stable structure erected over water to allow the docking of seacraft
<>    <>
- ApacheCON Y2K: Come to the official Apache developers conference -
-------------------- <> --------------------

View raw message