In the several projects that I have worked on that are
XML based, only a small amount of the XPath queries
are used for XSLT processing (unfortuneately).
Most of my XPath is querying "background" documents for
their data, most of which never gets displayed to the screen
or translated to another document. For example, in my
current project we query a database which returns
an XML document which then gets extensively queried
using XPath.
Hope this helps,
Eric
-----Original Message-----
From: Shane Curcuru [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 18, 2002 6:46 PM
To: [EMAIL PROTECTED]
Subject: RE: XPathAPI performance problems
---- you "Walsh, Eric" <[EMAIL PROTECTED]> wrote ----
> For the record I say you just throw the old routines back
> in and call it even, especially since very little of my
> XPath queries are XSLT originated.
I know there are definite issues with our XPathAPI performance, but I
think this is actually a bigger question about Xalan's direction. How
does this fit in with the (in my mind) goal to have Xalan be the most
conformant XSLT processor for running stylesheets in a variety of
situations.
It sounds like we have a lot more power users of our XPath
functionality than perhaps we had expected. But I'd be nervous if
XPath customizations caused instability or problems for our general
stylesheet users.
I guess part of this is also because we have a limited number of active
committers, so there's only so much we can do without more developers
submitting patches back and helping with the work.
(Maybe I'm just being paranoid, and we can make a few tweaks that will
help out the straight XPath users without affecting general stylesheet
processing...)
- Shane
=====
<eof aka="mailto:[EMAIL PROTECTED]"
"http://www.otnemem.com/"=.sig />
__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
