Re: CachedXPathAPI performance hit?

I would expect CachedXPathAPI to perform about as well as XPathAPI -- the 
main difference is that it requires explicit clean-up to release the 
cached copy of the document. But it's been a while since I looked at that 
code.

______________________________________
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
  -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (
http://www.ovff.org/pegasus/songs/threes-rev-11.html)