Chris, Here are some ideas you might want to review these options:
1. Try storing the data in the database as xml files them selves. You then do not have to create the xml file. This will no doubt increase your database size. 2. Store your xml templates in the database for faster retrieval. 3. Have the xml file reference the xslt file for the translation to occur on the client end...they get the HTML and all u really worry about is creating the xml file and having the xslt file. 4. Do the translation of Database -> XML -> XSLT -> HTML all in PHP and save the HTML output for caching. Then u can save a link to that file in your database. This will allow you to have a very good caching system. When a request for a page comes in u can verify if the cached link in the database is too old or not. Then you can either get the link to the cached file or get the data to create the XML file. But, I have a feeling that this will still be extremely sufficient for your speed requirements... On Tue, 2002-10-15 at 08:25, Chris Boget wrote: > Let me preface this by saying that I know the benefits of using > XML with regards to portability and extensibility. > Here is the issue I face. I have all of my data stored in a MySQL > database. I'm considering reworking my website so that it uses > XML (after being converted from resultant records in my DB) to > transmit & XSLT to transform and display the data to my end user. > There are a few benifits I can see in sending XML messages as > part of the back end processing. However, that seems to be out- > weighed by the amount of processing that's going to need to take > place in actually serving the data to the user. > First I have to query and pull the records from the database. Then, > I need to send those records to a function (or functions) to convert > it to XML. Then, I need to take that XML data and have PHP use > an XSL stylesheet to transform it to HTML before it, finally, gets > sent on to the browser. So that's basically 2 conversions that take > place on the back end. > How much experience have any of you had with doing that? Does > it take significantly longer to serve the pages; is there a noticible > performance hit? Do you realize more benifit for the back end > processes when using XML that makes any additional time it takes > to display a page to the user worth it? > I'd love to hear about people's experience with this kind of thing so I > can better make a decision wrt whether or not I should even go down > this route. > > thnx, > Chris > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php -- .: B i g D o g :. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
