attached is a very simple diagram i put together when i got home illustrating a possible relationship between the main components in an xsl templated php application w/ a database back-end. as ive mentioned there are other configurations as well. primarily the main options in the overall relationship are rendering the xhtml on the client or server side and building xml data in memory or reading in xml files from disk. also, this diagram does not take into account any sort of validation using DTDs or XMLSchemas. i am currently vaguely familiar w/ those technologies and therefore dont know how to incorporate them into the image.
actually to be quite honest i dont think the would really be used when generating a page to send to the client. really those are important if you expose an API and allow clients to send data to your application. then it would be handy to validate that xml w/ a dtd or xml schema. the other thing as i mentioned before is i cannot see a reason to create xml data while processing a GET or POST request from a client; it would just be an extra step with no apparent benefit as far as i can tell.
-nathan
On 7/12/07, Kelvin Park <kelvinpark86@xxxxxxxxx> wrote:
I'm trying to setup a XSLT based web site.
I wasn't exactly sure about the flow of the whole system when data from
relational database is transferred to XML and in turn the data inputted
from the user is relayed back to the database through XML (or directly
to the database with PHP DB connection). I built a flowchart
illustrating what the flow of the XSLT/PHP/MYSQL system might be like.
If you think it's the wrong way or an inefficient way of getting user
inputted data back to mysql, I would appreciate any comments.
If you cannot download the PDF file, you can bring it up with direct
address the the file: http://www.envigan.net/CMSFLOW.pdf
--
PHP General Mailing List ( http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
