On May 2, 2005, at 2:09 PM, Jan Schenkel wrote:
I'm wondering where you would need this, since most browsers to the job already as a matter of course...
Sivakatirswami
One reason to do it within your application is data security : if you display the XML in a browser, and refer to an XSL, you can hide certain data -- but if the user picks 'View the source' in his browser menus, he can see the entire XML file. Another reason to include XSL support is that it allows for context-management server applications: the programmer just delivers the XML, and the CGI-script (or Rev-built web-server) applies an XSL transformation to deliver for GPRS, WAP, PDA,... Yes it's more work for your server or your application if it's done beforehand, but it has its advantages.
Jan Schenkel.
Sivakatirswami,
I am looking into this because by pre-processing the XML/XSLT files, we can trust that even people using odd platfoms (symbian based smartphones, ZetaOS, etc...) will be able to see the HTML files. Also because I am thinking of ditching my own template engine in RevHTTPd in favor of XML/XSLT, thats why wanted to know if I could force the transformation on the Rev side.
if the Rev Team could expose the XSLT functions, then I'd be good to go, if it can't well, I can always create shell scripts and hook them with shell().
Cheers andre
-- Andre Alves Garzia 2004 BRAZIL http://studio.soapdog.org
_______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
