Subject: RE: [xsl] Design Issues in XSLT From: "WATKIN-JONES,ADAM (HP-UnitedKingdom,ex1)" <adam_watkin-jones@xxxxxx> Date: Wed, 10 Jul 2002 11:34:02 +0100 |
----- Original Message ----- From: "Emmanuel Oviosa" <Emmanuel.Oviosa@xxxxxxxxx> > Caching xsl templates into application variable seems to improve performance > but is there any serious issues on the use of application variables like we > have in sessions and cookies?. In case you are alluding to the scalability problems you can create by storing apartment threaded COM objects in application/session variables (thus reducing concurrency by forcing serialized access to the objects), then you may be pleased to learn that XSLTemplate has a threading model of Both. >From the MSXML4 docs for IXSLTemplate: 'To cache a compiled XSLT style sheet, load an XSLT style sheet into an IXSLTemplate object. This object is free-threaded and stateless, so it can be stored in shared Active Server Pages (ASP) application state.' HTH! Adam XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Design Issues in XSLT, Michael Kay | Thread | RE: [xsl] Design Issues in XSLT, Emmanuel Oviosa |
[xsl] Re: key() question?, Dimitre Novatchev | Date | RE: [xsl] include external JS file , Américo Albuquerque |
Month |