On Sat, 2010-01-02 at 18:50 +0100, Michael Müller-Hillebrand wrote:
Am 02.01.2010 um 15:54 schrieb Rob Belics:
I should add that I'm particularly interested in XSLT on the client
side.
Well, what benefits do you see?
You have to limit your users to certain browsers or test your application for
all browsers not only for their HTML/CSS but also for their XSLT support.
You send out XML fields as well as your own custom XSL programming logic.
Well, I love to learn from others for free...
Assuming your data source is XML already it is most likely not the kind of
XML which can be transformed into HTML by a browser. It is more likely some
stuff that shows some of your business logic. So you would have to transform
this data-XML into some form of publishing-XML anyway. Why not have the step
to publishing-HTML in the same process chain?
- Michael
The page displayed in the browser would be the same but only the
displayed data would change, as in my restaurant example. All the
surrounding elements would be the same, only the name of the for-sale
items, prices, descriptions, etc. would change. Such information would
be xml data and only that would need to be transferred from the server.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--