Subject: Re: [xsl] sax or dom in XSLT procesing ? From: Oleg Tkachenko <olegt@xxxxxxxxxxxxx> Date: Wed, 29 Jan 2003 11:49:28 +0200 |
:Of course SAX, don't waste memory for superfluous temporary DOM.The question was not about general events vs trees, but specifically, what's the most effective approach for feeding an xslt processor - emitting SAX events or building DOM object. Correct me if I'm wrong.
I don't think it was a fair answer. Both tokenizing and tree processing have their pros and cons. Advantages of SAX are:
Disadvantages of SAX are:I'd like to discuss it, but it seems to be sort of offtopic here.
* Easily forgets previous elements it worked on * Not easy to re-order elements * Cannot validate an XML document * Canot easily verify ID-REF links
In fact, SAX-like processors are used to produce DOM-like processors.That's why I have recommended SAX as input for xslt. If almost every xslt processor always builds internal tree from its input, I don't see any advantage of building possible huge DOM object just to move data.
-- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re[2]: [xsl] sax or dom in XSLT pro, Andrey Solonchuk | Thread | RE: [xsl] sax or dom in XSLT proces, Sherzod Ruzmetov |
Re[2]: [xsl] sax or dom in XSLT pro, Andrey Solonchuk | Date | Re: [xsl] sax or dom in XSLT proces, Oleg Tkachenko |
Month |