Sorry, I didn't see your previous answer.
Please ignore this.
Thanks.
On 7/17/06, Mohsen Saboorian <mohsens(_at_)gmail(_dot_)com> wrote:
Michael,
Is the term XSLT compiler (which is commonly used for tools such as
XSLTC, Gregor/XSLT, XSLJIT, etc) also applicable to Saxon. I mean, is
the API functionality of parsing (probably building a parse tree or
something similar for later use) which is provided in XSLTC, is also
available for other JAXP implementations such as Saxon?
Thanks.
On 7/17/06, Michael Kay <mike(_at_)saxonica(_dot_)com> wrote:
> >
> > Hi,
> > I want to cache an instance of a Transformer (e.g. using
> > Templates.newTransformer()) in the application scope of a web
> > application (multi-threaded). Is there any synchronization
> > problem with this approach (using Saxon)?
>
> I think I should perhaps have added that whether you reuse the Transformer
> really doesn't make a big difference. The important thing is to cache and
> reuse the Templates object, which represents the compiled stylesheet. Doing
> that is a very big saving, especially when the transformations themselves
> run quickly (because the input documents are small).
>
> Michael Kay
> http://www.saxonica.com/
>
>
> --~------------------------------------------------------------------
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
> To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
> or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
> --~--
>
>
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--