Re: Re: OOP vs procedural

Hi, There a few possibilty`s here i think: 1. Using CSS to display XML client side, however i think this is usualy a bad idea, mainly because not all browsers suppoit it 2. Using XSLT to transform your XML on the client(to XHTML), well same as the above, not all browser are yet capable of doing this, and you probably have more data in your XML file that you would like your client to see... maybe. 3. The best option is to use XSLT to transform your XML and doing it on the server. This adds flexiblity because now you can create multiple XSL stylesheets to transform your XML in the required output format, XML, XHTML, cHTML or whatever you may need. In case of a webbrowser on a PC/Mac your send the client gets valid XHTML, wich is HTML wich confirms to the XML standards;-) Just my 0,2 cents Info@Best-IT wrote:

I've heard a lot that XML is taking over. Is the browser going to read some kind of HTML or straight HTML. Take FlashMX for instance, you can build a movie which is essentially an application driven by XML. But the XML is like a Database with nodes instead of records. This can be dynamically generated and read by the Flash movie, but because it's flash. If you took that same flow and created an app that had a browser for the front end instead of flash player, how would you get the browser to understand what it needed to display? Are browsers going to be re-written? - Most likely my thought process is off track. Mainly I don't understand how a browser can read XML? R/T

Best regards, Davy Obdam -- ----------------------------------------------------------------------- Davy Obdam Web application developer Networking4all email: d.obdam@networking4all.com email: info@davyobdam.com internet: http://www.networking4all.com -----------------------------------------------------------------------