The bootstrap in any web-based application is important to get right, however Zend Framework makes us put in extra effort to do it right. So in the Zend Framework Bootstrap series we've seen a concise, time saving approach for taking a lot of the
pain (erm) effort away. But here we are at the end of the series. So like all good software projects, it's time for a bit of a retrospective on the series. Let's look over what was covered.
Part 1 - Getting Started
As you'll remember, in the first part of the series we laid the foundation for the series by talking about what the bootstrap is and what it does, specifically in the context of the Zend Framework. We followed that up by creating a custom bootstrap class and class library directory structure. Following this we added its namespace to the application ini and modified the default application bootstrap so that it extends from it. At this point, any application will start to have instant access to the wealth of resources that we're about to give it. We then rounded out the first part in the series by looking at one of the most important components - caching.
Part 2 - Factoring in Routing, Navigation and more…
Then, in the second part of the series, we built on the foundation laid in part one by creating plugin resources for the other most important components in web-based applications:
- The routing table
- Application navigation
- Datasource (database) connections
Part 3 - Placeholders and Resource Plugin classes
And finally in the third part of the series, we took a slightly different path from the previous approach and instead of creating bootstrap resource methods, we took the approach of creating resource plugins which made implementing placeholders and paginationjust a piece of cake. Why was this so? Because instead of the resource plugins, by using this approach, all the user needs to do is to add configuration options to the application.ini.
What are your thoughts?
So what did you think - yes you; you, sitting there at the keyboard, reading the iPhone on the train, reading the Android in the taxi? Did the work go far enough? Did it cover enough for it to be meaningful for you? How can you use this approach to bootstrapping in your next (or current) Zend Framework application?