hi all, XML + XSL is a powerful combination, but it works on selected browsers. to build a real world application one has to take care of the users using older version of browsers. and a webdeveloper cannot send a XML parser to each and every user, to tranform XML to HTML using XSLT. what is the other way to tackle the users using older versions of web browsers. how can XML files be converted to HTML without using a parser at client end.
For a public website, Client-side XSLT won't work; many broswers will not handle it. Even in a "controlled environment" where everyone uses the "same" browser and has access to the same resources, client-side XSLT can be problematic, or at least that was the case a couple of years ago when we dabbled with it.
We do XSLT on the server, producing straight HTML for the client.
There are two ways to do this. One is to write software that generates and XML document, and applies it to your XSLT stylesheet on the fly (for each request), the result of the transform being an HTML document. We write Java servlets which only focus on returning the XML needed for the page, then at the last moment execute the transformation. There are many, many good things about this approach. But it's not simple.
Or if you have static XML documents that contain the content data, you can generate the HTML as static files which you copy to your web server ane serve in the conventional way. This can be a lot simpler if you don't want to, or cannot control complicated server-side software and stuff. Of course it's a lot less flexible than the dynamic model.
Many tools are available to do either way. And in either case, you need not rely on any special capabilities of the browser to render your result.
I've seen some ATOM feeds providing XSLT as an alternative to their feed.
So if a normal user visits the feed from his or her everyday browser, he gets the HTML formatted version of the feed on the same URL, but when a robot or a crawler goes to it, it gets the original ATOM content.