Application Flow Chart of Codeigniter Application

Hello Friends,
                       Today I am  bought you the  cycle of codeigniter application how the request is made to the controller and how the controller interact with the route and the Model in order to run the application completely i show you with the application Flow chart of Codeigniter how it's take request and  send a response on to the browser as shown below and also tell  you how the applciation flow chart works when someone request it.

       Codeigniter Application Flow Chart

Step-1 :-In each and every Application Index.php page server as the first page of any application based on php as we are here talking about the codeigniter so as here the index.php server as the entry point of the application flow chart. It basically initializing the base resources needed to run the Codeigniter.

Step-2 :-  Here in the diagram you can see the word Routing in the Green Box. Basically Routing server the HTTP request which are coming from the index.php  and Routing is the one who determine what action will be fire as per the HTTP request which he been receiving from the Index.php page of the Application.

Step-3 :-  Below the Routing you can see the Caching Box which is basically used for caching . here if the cache file exists in the applciation the routing does not process further but it bypass the normal flow system of the application and move the the caching file and send it to the Browser Directly.

Step-4After this there is a Security Module which is loaded first before any Controller of the Application is loaded. Any request comes  or any data submitted to the application is filtered through the Security module of the Application.

Step-5 :-Now the main portion of the Application is the Application Controller which server the request coming from index.php through route to the controller. The controller of the Application  loads the loads the model, core libraries, helpers, and any other resources needed to process the specific request.

Step-6 :- The Final step is the View Module which 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.