xml - Browser rendering XSLT vs PHP rendering XSLT -


I use XML and XSLT in my current project and I would like to know if it is good to present the browser in XML HTML's with stylesheets instead of using something like PHP's XSLT processor.

One of the main reasons that the API uses XSLT processors allows API to access my XML data in the near future. So I want the conversion side of the client, so my XML is still available.

I may be wrong about the PHP XSLT processor, but when an XML is processed via PHP, then the received data in the render XML (my case HTML) and XML data is no longer available. Is it true?

Thank you for cleansing things.

It all depends what your ultimate goal is, I work on an application that reports Prepares us as XML and we send XML and XSLT in the browser to process. There are a few reasons for this approach:

  • As you've mentioned before, you can proceed further on the client
  • The HTML is verbose sufficiently and If you have control over specifying your XML you can ensure that it is not a verbose, in the end you send small amounts of data between the server and the browser
  • XSLT on the browser Be cached So that after the first use of the overhead
  • transforming on the server loads on your server so that you can affect many people trying to access the page at the same time Are there.

In some cases we transform on the server. Like we change into an HTML table and then change the http content type to send the result as an axle.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -