Re: xslt on server-side vs. client-side
----- Original Message ----- From: "Nathalie Pult" <s9292251@xxxxxxxxxxxxxxx> > Hi List, > I already worked with xslt on server-side. > What are the advantages and disadvantages having operations done on > client-side? Hello Nathalie, Your question is fairly generic, so i will be short. - Client side processing is desirable as this offloads processing from server to client, this is especially compelling when all that needs to be sent to the client is data, as stylesheets will already be cached. - It would be nice for all major browsers to be in spec for xslt processor, but unfortunately the only real choice is IE, though the IE xslt processor is exceptional ( did i say that ? ). Mozilla does have xslt support, but at the moment it is a bit sketchy but it should be up to spec very soon. When this occurs client side processing will become more ubiqitous. - client side processing, in a semantic world, means possibly that the browser will take in data from a whole range of remote servers, then aggregating this into a single customised 'view' at the client. - some of the really neat clientside stuff has been done by Chris Bayes at www.bayes.co.uk/xml chow, jim fuller XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format