RE: XSL processor authors - how about this approach?

Subject: RE: XSL processor authors - how about this approach?
From: "Steven Livingstone, ITS, SENM" <steven.livingstone@xxxxxxxxxxxxx>
Date: Mon, 13 Mar 2000 12:16:04 -0000
With the new MSXML processor (preview) you can create compiled XSL
stylesheet templates - pretty useful and fast.

Sounds like a similar idea to what you suggest.

Pro Site Server 3, Wrox Press
Pro Site Server 3.0 Commerce Edition, Wrox Press

Steven Livingstone
Glasgow, Scotland.
07771 957 280 or +447771957280

> -----Original Message-----
> From:	Dylan Walsh [SMTP:Dylan.Walsh@xxxxxx]
> Sent:	13 March 2000 11:41
> To:	xsl-list@xxxxxxxxxxxxxxxx
> Subject:	XSL processor authors - how about this approach?
> >Date: Wed, 08 Mar 2000 12:41:47 +0100
> >From: Eric van der Vlist <vdv@xxxxxxxxxxxx>
> >Subject: Re: NewBie Question - Dynamic XSL
> <snip>
> >In this architecture, the operation which is taking most of the cycles
> >is the parsing of the XSLT sheet (which can take several seconds) and is
> >most of the time cached.
> Has anyone considered this kind of solution for server-side XSL? :
> Take the stylesheet, parse it and generate a custom servlet to perform
> this
> transformation. Then everytime XML needs to be transformed, this servlet
> could be run. This approach is a bit like JSP. You can do thorough
> optimisation when creating the servlet. It may even be possible to
> identify
> sheets that don't need random access, and switch to serial mode for those,
> saving memory.
> I would think that having custom generated Java code to move the data
> around
> would be faster than trying to figure out the stylesheet at run time.
> Great
> potential here for a performance boost?
>  XSL-List info and archive:

This message is sent in confidence for the addressee only.
It may contain legally privileged information. The contents are not to
be disclosed to anyone other than the addressee. Unauthorised recipients
are requested to preserve this confidentiality and to advise the sender
immediately of any error in transmission.

 XSL-List info and archive:

Current Thread