----- Original Message -----
From: <[EMAIL PROTECTED]>
>
> Right on target. In a branch (not on trunk yet) on Xalan interpretive
I've
> done some work towards this in eliminating redundent path expressions
(both
> full and partial), also trying to supply API towards rewriting task. From
> my experience so far, this will be the #1 tool for great optimization...
> things like rewriting certain expressions to xsl:key... lots of things
you
> can do with index predicates... all sorts of fun things. XSLTC goes a
long
> way towards solving micro-optimization (loosely termed).
DTM/DOMImpl(XSLTC
> Source tree version) goes a long way towards solving the source tree issue
> (in concept... there's still a lot of work to be done). The next big step
> is to really do a lot of work on these rewrites and special internal core
> language (like isFirst()). This will really be required for XSLT
2.0/XPath
> 2.0/XQuery.
Are you saying we can write something like:
<xsl:apply-templates select="//page[@id=$id]"/>
and it will be as fast as:
<xsl:apply-templates select="key('pages_key', $id)"/>
?
Does this have to be cached to work? Does it have to be XSLTC?
best,
-Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
