XSLT speed comparisons

[uche.ogbuji at gmail.com]

uche.ogbuji at gmail.com wrote:
> For what it's worth I just developed, and switched to WSGI middleware
> that only does the transform on the server side if the client doesn't
> understand XSLT.  It's called applyxslt and is part of wsgi.xml [1].
> That reduces server load, and with caching (via Myghty), there's really
> no issue for me.  For more on WSGI middleware see [2].
>
> [1] http://uche.ogbuji.net/tech/4suite/wsgixml/
> [2] http://www.ibm.com/developerworks/library/wa-wsgi/

I just wanted to clarify that not only does the applyxslt middleware
approach reduce server load, but in the case of clients running IE6 or
IE7, the XSLT *does* end up being executed in MSXML after all: MSXML on
the client's browser, rather than on the server.  In the case of
Mozilla it's Transformiix, which is between MSXML and 4Suite in
performance.  Not sure what's the XSLT processor in the case of Safari
(only the most recent versions of Safari).  But regardless, with that
coverage you can write apps using XSLT, support the entire spectrum of
browsers (and mobile apps, spiders, etc.) and yet rarely ever require
XSLT applied on the server side.


> --
> Uche Ogbuji                               Fourthought, Inc.
> http://uche.ogbuji.net                    http://fourthought.com
> http://copia.ogbuji.net                   http://4Suite.org
> Articles: http://uche.ogbuji.net/tech/publications/