From 8ede1a2ecbb62577afd32996956c5feaf7ddf9b6 Mon Sep 17 00:00:00 2001 From: Derek Jones Date: Wed, 5 Oct 2011 13:34:52 -0500 Subject: replacing the old HTML user guide with a Sphinx-managed user guide --- user_guide/overview/appflow.html | 95 ---------------------------------------- 1 file changed, 95 deletions(-) delete mode 100644 user_guide/overview/appflow.html (limited to 'user_guide/overview/appflow.html') diff --git a/user_guide/overview/appflow.html b/user_guide/overview/appflow.html deleted file mode 100644 index fbc68fab0..000000000 --- a/user_guide/overview/appflow.html +++ /dev/null @@ -1,95 +0,0 @@ - - - - - -Application Flow Chart : CodeIgniter User Guide - - - - - - - - - - - - - - - - - - - - - -
- - - - - -

CodeIgniter User Guide Version 2.0.3

-
- - - - - - - - - -
- - -
- - - -
- - -

Application Flow Chart

- -

The following graphic illustrates how data flows throughout the system:

- -
CodeIgniter application flow
- - -
    -
  1. The index.php serves as the front controller, initializing the base resources needed to run CodeIgniter.
    2. -
  2. The Router examines the HTTP request to determine what should be done with it.
    3. -
  3. If a cache file exists, it is sent directly to the browser, bypassing the normal system execution.
    4. -
  4. Security. Before the application controller is loaded, the HTTP request and any user submitted data is filtered for security.
    5. -
  5. The Controller loads the model, core libraries, helpers, and any other resources needed to process the specific request.
    6. -
  6. The finalized View is rendered then sent to the web browser to be seen. If caching is enabled, the view is cached first so -that on subsequent requests it can be served.
    7. -
- - - - -
- - - - - - - \ No newline at end of file -- cgit v1.2.3-24-g4f1b