From c576995304fc3609cca0b7b92d1b2cd611ec82f5 Mon Sep 17 00:00:00 2001 From: Andrey Andreev Date: Wed, 16 Jan 2019 17:49:35 +0200 Subject: [ci skip] 3.1.10 release --- user_guide_src/source/overview/appflow.rst | 23 ----------------------- 1 file changed, 23 deletions(-) delete mode 100644 user_guide_src/source/overview/appflow.rst (limited to 'user_guide_src/source/overview/appflow.rst') diff --git a/user_guide_src/source/overview/appflow.rst b/user_guide_src/source/overview/appflow.rst deleted file mode 100644 index bb15130d2..000000000 --- a/user_guide_src/source/overview/appflow.rst +++ /dev/null @@ -1,23 +0,0 @@ -###################### -Application Flow Chart -###################### - -The following graphic illustrates how data flows throughout the system: - -|CodeIgniter application flow| - -#. The index.php serves as the front controller, initializing the base - resources needed to run CodeIgniter. -#. The Router examines the HTTP request to determine what should be done - with it. -#. If a cache file exists, it is sent directly to the browser, bypassing - the normal system execution. -#. Security. Before the application controller is loaded, the HTTP - request and any user submitted data is filtered for security. -#. The Controller loads the model, core libraries, helpers, and any - other resources needed to process the specific request. -#. 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. - -.. |CodeIgniter application flow| image:: ../images/appflowchart.gif -- cgit v1.2.3-24-g4f1b