[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Speed: xsl with xml vs. html and the world
Before this conversation gets too far down the road maybe some clarification as
to whether you are referring to serving up XML that is then transformed by the
client using a referenced XSLT file or XML that is first transformed on the
server and then served up as HTML. If your question is concerning doing
everything on the server then what Josh Canfield stated would be pretty hard to
argue with. However, if you are referring to serving raw XML to the client for
client side transformation then your question definitely becomes more subjective
to many possible factors: client hardware + xsl processor being used etc...
If you are speaking of server side transformation to subsequent HTML stream you also need to consider the fact that most modern day web servers are smart enough to cache often used transformations and as such the difference between static and dynamic content will only be seen during the first request for the file and will be negligible at best for all subsequent requests if the source xml and xslt have remained unchanged since the previous request. With this in mind its tough to argue whether transforming an entire site into HTML first and then serving it as static content makes more sense than simply letting the web server worry about the optimization of content serving and you worry about what that content is going to be and what it should look like. This argument becomes even more prevalent when you consider a web that is comprised of more than just a typical desktop or laptop. With handheld devices and web appliances added to the equation the abilities of a web server to optimize requests becomes that much less of a luxury and more of a necessity as it allows you to focus on creating templates that can morph the HTML to conform the intricacies of the requesting form factor instead of worrying about building static HTML for each of these form factors and then telling your web server which one should be served to which client. The management of such a system would be a monster. Hope this helps clarify things a bit! Best regards, <M:D/> Amir Yiron wrote: I agree with you, Daniel. It's not a black & white question. It depends in many parameters. For example, the use of xml/xslt could save a lot of traffic in the net if your final HTML shows a large table - because the XML has only the pure data used for every row, and the graphic representation of a row (which is usually much larger than the pure data) is given once in XSLT, and not duplicated for every row as in HTML...
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|