MYSQL -> PHP -> XML/XSLT
Posted: Wed Jul 25, 2007 5:53 am
Hi,
This issue has already been discussed, I think. Nonetheless I want to ask you about my own problem concerning a design pattern I want to implement.
I want to separate PHP from the view.
Therefore I transform the data received by the DB into XML and use XSLT for styling it.
I have to mention that I would need to convert the XML into .csv or .xls, .pdf, .doc for exporting purposes.
Now I'd like to ask you if this approach affects the performance in a very negative way (I know that it affects it in a negative way but how much??) or if it could be a very modern approach.
IMHO I like the pattern but doubt that it will be very fast.
I'd like to give you more information about my plans:
There is a central .map.xml for every entity which serves for automated input processing and validation. Furthermore I'd like to use these Mapping files for creating the DB and INPUT-VIEWs.
For the Views - such as lists or single views - I would generate .xml templates, whose tags are the names of the DB-cols...
These xml templates are filled with DOM.
Now tell me what you think of that.
I appreciate any comment.
Cheers,
Peter
This issue has already been discussed, I think. Nonetheless I want to ask you about my own problem concerning a design pattern I want to implement.
I want to separate PHP from the view.
Therefore I transform the data received by the DB into XML and use XSLT for styling it.
I have to mention that I would need to convert the XML into .csv or .xls, .pdf, .doc for exporting purposes.
Now I'd like to ask you if this approach affects the performance in a very negative way (I know that it affects it in a negative way but how much??) or if it could be a very modern approach.
IMHO I like the pattern but doubt that it will be very fast.
I'd like to give you more information about my plans:
There is a central .map.xml for every entity which serves for automated input processing and validation. Furthermore I'd like to use these Mapping files for creating the DB and INPUT-VIEWs.
For the Views - such as lists or single views - I would generate .xml templates, whose tags are the names of the DB-cols...
These xml templates are filled with DOM.
Now tell me what you think of that.
I appreciate any comment.
Cheers,
Peter