[Home] [By Thread] [By Date] [Recent Entries]
At 00:11 22/06/2000, Dan Morrison wrote:
George Prezerakos (ETG) wrote:[snip] However, If you plan on moving your XSL transform to the client sometime in the future, then the question is like "How do I obfuscate my super-clever HTML?". And believe me - that way leads to madness <MADNESS view="source" href="http://www.nationalbank.co.nz/calculators/default.asp" /> Client-side encryption of code is, by definition, broken. Why? Because you have to provide: the encrypted code, the decryption engine, and the decryption key. So all the person at the client side is read these, and decrypt the code. Think of it this way: the web browser needs to understand it eventually ... J ------------------------- James Robertson Step Two Designs Pty Ltd SGML, XML & HTML Consultancy Illumination: an out-of-the-box Intranet solution http://www.steptwo.com.au/ jamesr@xxxxxxxxxxxxxx XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|

Cart



