On Wednesday, March 13, 2002, at 01:58 PM, Anas Mughal wrote:
> http://www.devshed.com/Server_Side/XML/XSLTrans/print Actually, that's the very tutorial that led me to ask about installing with XSLT configure parameters. I'm building it now, as I write this. But I was wondering about some XSLT/PHP style advice... How much of a burden does on-the-fly XSLT place on the server? I mean, relative to a typical setup. I'm playing with the idea of changing all my old HTML to proper XML files, and having PHP generate XML rather than HTML (seems trivial, since PHP doesn't really care what markup language I use to output data -- I could even do it in plain text if I was so inclined). But as PHP generates the XML, there is another step now, and that is the step of running the XML data through one of the XSLT functions (such as xslt_create && xslt_run or xslt_process). I'm sure that it all depends on the strength of the server being used, but does anyone have a rough estimate of what kind of burden this extra processing has? Or a reference? Speed isn't the biggest concern, since I don't have a large number of users like some public sites. Mine is an internal site, run off a Linux server w/256MB RAM. But it seems like a lot of work for Apache to process the incoming request, hit up the PHP script, fetch data from MySQL, format the database output into XML, and then run the XML through XSLT to get HTML. And to answer the question "do you really need your data in XML?", the answer is no, but this kind of thing gives my boss something to brag about to visitors: "this is our temp, he's building our internal schedule-managing database-driven XML-based web application...we pay him little more than minimum wage and he gets no benefits, but he's happy with the work." Plus, it'll look good in the portfolio. Thanks in advance, Erik -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
