| Derek Jones | 8ede1a2 | 2011-10-05 13:34:52 -0500 | [diff] [blame] | 1 | ###################### |
| 2 | Application Flow Chart |
| 3 | ###################### |
| 4 | |
| 5 | The following graphic illustrates how data flows throughout the system: |
| 6 | |
| 7 | |CodeIgniter application flow| |
| 8 | |
| 9 | #. The index.php serves as the front controller, initializing the base |
| 10 | resources needed to run CodeIgniter. |
| 11 | #. The Router examines the HTTP request to determine what should be done |
| 12 | with it. |
| 13 | #. If a cache file exists, it is sent directly to the browser, bypassing |
| 14 | the normal system execution. |
| 15 | #. Security. Before the application controller is loaded, the HTTP |
| 16 | request and any user submitted data is filtered for security. |
| 17 | #. The Controller loads the model, core libraries, helpers, and any |
| 18 | other resources needed to process the specific request. |
| 19 | #. The finalized View is rendered then sent to the web browser to be |
| 20 | seen. If caching is enabled, the view is cached first so that on |
| 21 | subsequent requests it can be served. |
| 22 | |
| 23 | .. |CodeIgniter application flow| image:: ../images/appflowchart.gif |