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.
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. Worse, it
may add performance penalty for using LazyDOM with reloading.
Chris's patch allow us to make LazyDOM template for the reloading. So,
the LazyDOM tree constructed from the reloading can benefit from the
performance enhancement of LazyDOM in typical XMLC usage pattern.
David Li
| 