Re: Moving XMLC to Xerces 2 won't help...

On Friday 24 January 2003 11:11, David Li wrote:
> > The LazyDOM as it is doesn't play very nice with the new
> > reloading code (the main problem is that LazyDOM is optimized for the
> > case of
> > constructing the template DOM "by hand" in the methods generated in
> > each
> > class, whereas the new reloading code parses the DOM template from a
> > file),
> > and I think we're all agreed that XMLC needs a bit of refactoring to
> > disentangle its internals :-)
>
> Regarding to LazyDOM and new reloading, Chris Webb has sent me a patch
> that would make those two play nicely. I haven't gotten around to
> integrate it yet.

Great to hear this.

> Basically, the problem with reloading and LazyDOM is that it copies the
> whole document tree in every request. This makes the reloading code not
> to be able to benefit from LazyDOM's performance enhancement. 

Exactly.

> Worse, it may add performance penalty for using LazyDOM with reloading.

Actually, no - I've made a couple of measurements on an application that uses 
the new relaoding code, and I didn't notice any significant differences in 
load times between LazyDOM and Xerces DOM.


-- 
Richard Kunze 

[ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg
Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1
http://www.tivano.de, kunze@xxxxxxxxx