> No offense meant, but most people start with the most
> inefficient ways to generate XML, usually doing a
> lookup in a remote database (which is slow, but hard to
> avoid), building an XML string or a DOM tree (which is
> slow, memory consuming and avoidable) and then feed it
> to the XSLT processor.

I meant to ask--what alternatives do you suggest to that avoidable second
step as far as getting to the XSLT processor?

thx a lot

Matt Savino


Reply via email to