[xsl] Design Issues in XSLT

Subject: [xsl] Design Issues in XSLT
From: "Emmanuel Oviosa" <Emmanuel.Oviosa@xxxxxxxxx>
Date: Wed, 10 Jul 2002 09:56:42 +0100
Is XSLT matured enough for the development of a multi-tier web application
that will be used in many regions across the country by 100s of users?.
Developing in XML, XSL, COM+, VB, SQL 2000, JavaScript, ASP.

Does anyone know for sure that XML/XSLT approach would be faster, scalable
and more maintainable than the ASP/ADO approach, is there any bench mark

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?.

Should I be calling my MTS VB components in the XSLT, do I even need ASP?.

Is there any overhead in passing MSXML DOM object accross com boundaries,
should I be passing xmldom.xml instead?

A lot of questions maybe but there is a million pound waiting for the person
with the best answers, only kidding.

Michael, Jenny or anyone else with a good knowledge of XML/XSLT should
please respond.


The contents of this email and any attachments may be privileged or confidential, for the exclusive use of the intended recipient(s) only and may not be disclosed or used in any way other than by the addressee(s). If you have  received this email in error please advise the sender and delete from your system.

Integrated Solutions Consultants Ltd are unable to guarantee the security of email content outside of our own systems where all emails and content are treated in accordance with the Regulation of Investigatory Powers Act 2000.

Further information about Integrated Solutions Consultants Ltd is available at http://www.isc.co.uk or mailto:info@xxxxxxxxx

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Current Thread