|
Not necessarily. The transformations can easily be done on the server (I usually run in a servlet container) and the XSLT's can be compiled so the transformation is pretty cheap.The combination of XML data and XSLT transformation(s) into XHTML is verypowerful.
Powerful as in flexible, yes, but it comes at a cost. That XML had to first
be serialized on the server, deserialized on the client, then the response
would need to be serialized on the client and deserialized on the server.
There are a good number of CPU cycles used in the name of open spec
technologies.
If you own both ends of the spectrum (i.e. the server language the theThen you need to first define what "Efficient" means, and how to measure it.
client Javascript) then why not come up with a solution that is more
efficient? Note that I am just introducing this argument into the
conversation and am currently somewhat of an offender of using popular data
transmission mechanisms simply because they were quick to implement (i.e.
ExtJS + JSON + RPGUI).
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.