RE: XSLT on the server side

If you want to use Saxon, start by looking at the sample servlet code that
comes with the product. You'll see that it caches compiled stylesheets (but
not source documents or results). You could modify the servlet if you need
to, to do other kinds of caching according to your application requirements.

Michael Kay
http://www.saxonica.com/

> -----Original Message-----
> From: Antsnio Mota [mailto:amsmota@xxxxxxxxx]
> Sent: 02 September 2005 18:42
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  XSLT on the server side
>
> Thanks. But as i'm not a expert on that, that raises me a question.
> The caching of both stylesheets and results of transformations are
> made by who? The processor, like Saxon? Or the web server?
>
> Now, i'm using a XSLTProcessor (in Sarissa) that allow for xslt
> reusability, will it be someone like that?
>
> I'm sorry if this questions are too dumb, but...
>
> On 9/2/05, Jay Bryant <jay@xxxxxxxxxxxx> wrote:
> > > Whatever approach you choose, if you have any signicifant level of
> > > throughput, make sure that you cache compiled stylesheets
> in memory rather
> > > than recompiling them on each request.
> > >
> > > Michael Kay
> > > http://www.saxonica.com/
> > >
> >
> > From the category of experiences worth remembering: When I
> was a contractor
> > at Interleaf (and then an employee at Broadvision), I
> worked on an XML-based
> > document management product (Bladerunner). The system
> stored documents as
> > trees of nodes in a database. We found that users tended to
> request the same
> > documents many times rather than each request being a new
> document. So, we
> > cached the results of each query and the resulting
> transformation and got a
> > significant performance boost (on the order of halving our
> average response)
> > for our trouble.
> >
> > So I suggest you give result caching a try, too. As ever,
> YMMV (maybe your
> > users aren't as repetitive as ours were).
> >
> > Jay Bryant
> > Bryant Communication Services