Re: FW: XSL with scripting

Subject: Re: FW: XSL with scripting
From: Keith Visco <kvisco@xxxxxxxxx>
Date: Mon, 21 Dec 1998 13:11:53 -0500
Paul,

Actually I have my own XSLProcessor that does accept a DOM Document for
the source...


--Keith

Paul Prescod wrote:
> 
> Keith Visco wrote:
> >
> >  We query a couple of different databases and turn the query result into
> > an XML document. Depending on the request, we can return just the XML or
> > we can run it through a stylesheet. The reason we allow returning the
> > XML is so that we can provide a service to any other applications
> > wishing to get at the data. Its actually quite efficient, thought I do
> > agree that it would be faster just to convert the data into the desired
> > format. We lose the flexibility of the stylesheets if we do that and we
> > decided that the tradeoff was in favor of XSL.
> 
> If you want to avoid the XML-text step, why don't you build a tree
> directly from the results of the query and sic an XSL processor on
> the tree. Of course you would have to hack the XSL processor to accept
> your tree instead of a text file, but that shouldn't be too hard.
> 
> You could even map your entire database into an XML-like structure and
> then write an XSL processor that treats the database as the input
> document and creates some particular result document. This is a
> much harder proposition because you must map your database schema to
> XML nodes and your XSL patterns into SQL queries...but it might
> provide even higher performance depending on your application.
> 
>  Paul Prescod  - ISOGEN Consulting Engineer speaking for only himself
>  http://itrc.uwaterloo.ca/~papresco
> 
> "Are the social and economic benefits of capital punishment sufficient
> to outweigh the injustice of accidentally executing innocents?"
> "What benefits???"
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread