[Home] [By Thread] [By Date] [Recent Entries]
Hi John,
It would certainly be easiest to use the parentid attribute. To do In most (good) XSLT implementations, a hash table for the key will only be generated when/if the key() function is first invoked, and that hash table will be around for the remainder of the transformation. Using a key is usually faster than using an equivalent path (and much faster than trying to interpret an XPath using XSLT). The only thing you really have to worry about if you're using keys with a large document is how much memory the key's hash table will take up. I don't know details of ASP.NET, but keys are bound to single transformations and as such they won't be cachable across invocations of a stylesheet. If you run into performance problems, you might have more luck from an XQuery implementation, since they're designed to work with databases in which permanent indexes are possible. Cheers, Jeni -- Jeni Tennison http://www.jenitennison.com
|

Cart



