RE: Design Issues in XSLT

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

The technology is mature enough, but are the developers? Only you can
answer that.

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

No, no-one knows this for sure. And the same remark applies:
performance, scalability, and maintainability have much more to do with
the skills of your developers than with your choice of technology. Of
course, one of the benefits of using XSLT is that you aren't locked into
the Microsoft platform. Perhaps that's something your company doesn't
care about, but after this year's licensing changes, perhaps it should.

> 
> 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?
> 
I certainly don't know enough about the Microsoft platform to advise you
on the details here. I leave that to the guys with the screwdrivers and
MCSE badges.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 


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