On Tue, 17 Sep 2002, Michael Brennan wrote:
> Jaxen currently takes a lazy approach to resolving namespace prefixes to
> URIs. I see some usability aspects this provides (e.g. being able to use
> the "addNamespace" methods on an already created XPath), but I also see
> that this resolution gets done over and over again with the evaluation
> of each name test or namespace test in an XPath or Pattern. This seems
> rather wasteful, doesn't it? Has there been any discussion of
> refactoring this, or is the team pretty firmly wedded to keeping things
> as they are?
One thing to note. Folks may be passing in different NamespaceContext's
that do different prefix-uri bindings. Dunno what the use-case is, but
just wanted to throw it out there.
-bob
-------------------------------------------------------
This SF.NET email is sponsored by: AMD - Your access to the experts
on Hammer Technology! Open Source & Linux Developers, register now
for the AMD Developer Symposium. Code: EX8664
http://www.developwithamd.com/developerlab
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
