What is faster for you if you work with a dom in memory.

1\  To create a reader with the dom and next to pass the reader to create a
dtm.
2\ To work with DOM2DTM

I currently work with xml4j and I have probleme with the DOM2DTM, but if
it's much faster than the first solution, i'm going to try more.

Jean-Jacques Borie
Directeur recherche et d�veloppement

Tekora, changez votre conception des sites web
http://www.tekora.com
17, place de la R�sistance - 92130 Issy-les-Moulineaux
T�l. : +33 1 55 00 10 03 - Fax : +33 1 55 00 10 10
Por: +33 660199524
[EMAIL PROTECTED]

Pour vous inscrire � la Newsletter Tekora :
http://www.tekora.com/tekora/fr/12_1.html



                                                                                       
                                                         
                    Joseph_Kesselman                                                   
                                                         
                    @lotus.com              To:     [EMAIL PROTECTED]           
                                                         
                                            cc:                                        
                                                         
                    21/09/2001 18:23        Subject:     RE: Xerces DOM Objects & 
Xalan                                                         
                    Please respond                                                     
                                                         
                    to xalan-dev                                                       
                                                         
                                                                                       
                                                         
                                                                                       
                                                         





>latest versions of Xalan-J use a new internal model, called the DTM. If
you
>pass in a DOM source, Xalan will build a DTM model of that DOM and
>transform the DTM, so you're right back where you started from since you
>still have two copies of the document.

Slight quibble: Xalan-J builds a DTM _proxy_ to the DOM. A fair amount of
information does wind up being replicated for speed-of-execution reasons,
but we do avoid recopying #PCDATA, and some of the other info is also
retrieved from the DOM only when needed. And we build the proxy
incrementally, which may allow us to avoid constructing all of it.

So DOM2DTM isn't really a "second copy" of the DOM document. But yes, the
proxy layer does impose a significant amount of overhead compared to the
"native" DTM.





Reply via email to