Subject: Re: [xsl] Practicality of Separating Data from Presentation From: "James Fuller" <james.fuller@xxxxxxxxxx> Date: Tue, 2 Jul 2002 00:39:31 +0100 |
+1 to that ! I am now hitting performance walls with XSLT in many situations, not to mention that there are serious problems with doing simple RDBMS thingies, i''ll be the first in line to implement commercial XQuery solutions, when they cheapen and flourish, of which they are not at the moment. cheers, jim ----- Original Message ----- From: "J.Pietschmann" <j3322ptm@xxxxxxxx> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Sent: Monday, July 01, 2002 9:05 PM Subject: Re: [xsl] Practicality of Separating Data from Presentation > James Fuller wrote: > > you will find that there are people out there that *gasp* hate XSLT for many > > reasons; > > - XQuery people think its a bit wimpy in real data situations, true but its > > simplicity means it gets adopted, even people who use XML have some problems > > with XSLT. The fact remains that XSLT solves most of XQueries use cases. > > Even better: Use a highly optimized XQuery engine to > query the terabyte data pool and produce XML, then > use XSLT to transform the query result into the > desired presentation. Concerns separated, everybody > is happy. No need for extremists, on either side. > > J.Pietschmann > > > 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 |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Practicality of Separatin, J.Pietschmann | Thread | Re: [xsl] Practicality of Separatin, intelikon |
[xsl] Schema Optimsations Was XSL: , Kevin Jones | Date | Re: [xsl] Practicality of Separatin, James Fuller |
Month |