Cart
[Home] [By Thread] [By Date] [Recent Entries]
> From: Michael Kay [mailto:michael.h.kay@n...] <snip/> > I think the number of cases where you can do this > automatically is rather limited, though it might become > rather more feasible if the optimizer has knowledge of the > schema. It only takes a single template that uses "..", or a > leading "//", or <xsl:number/>, or key(), or various other > things, to make the optimization invalid, unless you know for > certain that these are only selecting within the current subtree. What if you avoid such constructs? What if all your expressions only select along the child and attribute axes -- are existing XSLT engines (SAXON, for instance) smart enough to optimize for that and not try to hold the entire document structure in memory?
|
