Re: [xsl] Newbie question on XSL transformations: multiple sorts on element attr

Subject: Re: [xsl] Newbie question on XSL transformations: multiple sorts on element attr
From: Marco <spinmar@xxxxxxxxx>
Date: Thu, 08 Feb 2007 14:24:17 +0100
Abel Braaksma ha scritto:
Marco wrote:

Because I'm trying to obtain best performance in the business logic and separate logic from presentation.
For example if my business logic takes 300 msec and my xslt trasform takes 30 msec, I'm happy because even if xslt trasform takes 10% I have separated data from presentation. The same logic in perl takes 600 msec, and xslt trasform takes always 30 msec or similar and so on.
So I'd like to use saxon in c because it offers xslt2 support but in the same way I'd like to continue to use c because my business logic is faster.
This my modest opinion.
Do you make provision for porting saxon in c?

..... but since .NET and Java together cover close to 99% of the operating systems, .........
I don't think so.

And like you say above: if your business logic take 300 msec and your xslt transform takes 30 msec, there is nothing more you need to do. Make sure you cache the compiled stylesheets, that will save you a lot of overhead.
The stylesheets are already compiled.

I have no idea why you think "xslt transform always takes 30 msec", ......
Original "xslt trasform takes always 30 msec or similar": it means the xslt transform takes one time 30 msec, one time 28msec, one time 34 msec, and so on.
I always use libxml2 and libxslt. You can use them in many languages and obviously also in perl. there is the porting of libxslt in many languages.

Perl is, like XSLT an interpreted language. Perl will be much faster in many respects, in other respects, XSLT will be. C will only be faster in cases where you optimize as much, but you will loose your flexibility. If you use C for your transformations, you do not need XSLT.
Maybe I was not clear. I'm talking about a xslt engine. Now I'm using libxslt and I'm very happy. I'd like to test my environment using xslt2: so I need a xslt engine (for example saxon) which supports xslt2. But I want to mantein my business logic in c and continue to use only one language.
Best regards


Current Thread