Michael Champion wrote:
> I'm not sure how that will ever
> change; for example, people are still fiddling with their SQL code and
> table organizations to get optimal performance rather than simply
> trusting the implementations. Why will that be different for
> XPath/XQuery?
I believe Daniela's point is that people shouldn't come up with
home-brewed XML processing engines nowadays just as nobody's writing
home-brewed database engines anymore. XML processing shouldn't be a
matter of art, while it shouldn't perform poorly by default neither.
Imagine a guy who only wants to rename some elements in an XML document.
SAX filter/custom XmlReader is one way to go, 10-lines XSLT stylesheet
is another one (and a better one as being declarative).
The sad thing is that XSLT impementations currently aren't smart enough
to realize that such XML transformation can be done in a streaming way,
so XSLT way's perf will be definitely worse and XSLT will definitely be
the one to blame.
--
Oleg Tkachenko
http://blog.tkachenko.com
Multiconn Technologies, Israel
