This question is asked very often. Serach this mailing list to read
more. The simplest answer is, that time consumed by xml processing
(compiling) is not so painful. Anway there are some attempts to cache
precompiled scripts, which sould be avaliable in few weeks/monthes.
My personal opinion is, that you can save many time using the right
template desing and strategy. The new release (to be released in few
hours) brings some efficiency improvements, try it, please.
And at last but not at least: XSLT is powerful engine and is more
complicated and slower then scanning the text in plain mode. I can't say
if 5-times is to much or not. It strongly depends on your design.
Feel free to ask more specific questions.
Radovan Semancik wrote:
> Hi!
>
> We develop a Perl application server based on XML. We use proprietary
> XML filter to convert XML output to HTML. I was looking on Sablotron as
> a solution, but my bncmarks shows that Sablotron is cca 5 times slower
> than our ancient pure-perl (pattern based) proprietary XML filter.
>
> I suppose this is due to sablotron's parsing of stylesheet for each and
> every transformation. Is there a possibility to pre-process stylesheet
> once, and process many XML documents with this pre-processed stylsheet?
--
Pavel Hlavnicka
Ginger Alliance Ltd.
Prague; Czech Republic
