#lifecylce

[topnach]

Man!! Where has 25 years gone! From that 19" 4lbs 7oz bundle of joy to the 6' 1" #Man you have become. It's seems time has flown by. But in reflection its been a road of memories I wouldn't a change a thing. I can only pray too see what the next 25 years have in store for you. For now, I say Happy Birthday #Son! I love you take each day at a time. #FathertoSon #SontoFather #lifecylce #blessed #legacy (at Phoenix, Arizona)

[laravelio]

The Lifecycle of a Laravel Request Part 2

Today we're going to finish learning the basics of the Laravel request lifecycle. Last time we read the public/index.php file and the laravel/core.php file. Today we'll continue by finishing laravel/laravel.php. After laravel/core.php is loaded laravel/laravel.php will handle the following tasks: 1. setup error and exception handlers 2. temporarily enable all php errors 3. start the default bundle (your application folder) 4. register a catch-all route. if your application or bundle's routes don't respond to a request, the catch-all will and it returns a 404 5. grab the language information from config and set the current language based on the uri 6. finally Laravel requests the route information from the router and calls the routed code, capturing the response into a variable 7. the response is then rendered to a string from the response object 8. the session is then saved using the chosen session driver 9. finally, the laravel.done event is fired and passed the response object **Our Goal for the Day** It's all pretty straight-forward here. But, we need to read the code and understand what it's doing so that we can leverage this knowledge going forward. Today's topic completes our reading of public/index.php, laravel/laravel.php, and laravel/core.php. Post any questions in the comments below. **Required Reading** [laravel/laravel.php](https://github.com/laravel/laravel/blob/master/laravel/laravel.php)

[borislit]

An excellent explanation of HTTP servlet lifecycle