On Sun, 2004-03-14 at 13:17, Jabro wrote: > Hi List, > hope somebody here can help me out here. For a new page I'm designing I see > one problem coming up. > As I need to generate varius outputs such as HTML or PDF I think going over > XML isn't a bad idea. > I create one XSL for my output and change the XML for Customer A or B behind > it. > Now how do I make sure customer A doesn't see customer B's XML file? I could > generate the XML for > every time I need it or store it as a blob are some of the ideass that came > in my mind. > Has anybody an idea on how to solve this? Are solutions for this available? > Customer A + B have to identify thru an authentication mechanism with PHP of > course.
if your authentication is designed correctly you should not have an issues with cust. a seeing cust. b xml files. That is really irrelavent as an xml architecture. What i would do is have separate xml and xsl(t) files for each customer that would be used to create the desired output....now the beauty with xml and xsl(t) is that you can use inheritance as well. I would have a global xml and/or xsl(t) files that contains generic or global requirments. Then the customer xml files can inherite from the global ones. This has helped me with major xml projects. Use schema to do the validation since that support inheritance as well. You can create the xml files on the fly or store them in a database or filesystem. I have used oracle xml datatypes with great success. Oracle has many great built-in features for xml that are fantastic. There are some php classes that probably have been created for dealing with xml to get you started. -- Ray -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
