"Behind the Scenes" ... here's how a ds/X front end application (ie: search.php) works.
| 1. | First, the application reads in the configuration settings from the file data/config.inc |
| 2. | Once this is read into memory, ds/X has the database connection information, and then makes one or two database connections (depending on whether or not there is a db cluster installed) |
| 3. | ds/X will then read in any other system level items from the database, such as internal templates, language settings, etc. as globally accessible objects for the rest of the application to have access to. |
| 4. | dsX then decides which application is being run, and loads that application's modules into memory |
| 5. | Once loaded, dsX creates a new application "object" and then sends program control to the object's "init_application()" method, which does all of the "thinking" and generating and database queries required to run the task that the person using the browser has requested. |
| 6. | ds/X Then fires up the template engine, and sends it the application object, and the requested template name. |
| 7. | The Template engine looks for "plugin" tags, and merges actual output from the application object with the plugin tags in the template to create the final HTML |
| 8. | Once the merge is complete, dsX output's the final HTML to the browser. |
We'll address each of the above steps in detail, in the following chapters of this document.
This help file was created with an unregistered evaluation copy of Help & Manual. © EC Software. All rights reserved. This message will not appear if you compile this help file with the registered version of Help & Manual.
