By: Alex Gervasio

Hey Kev,
Just to make things a little bit clear, you only need one .htaccess file to get the whole request/route/dispatch/response cycle up and running. From that point onward, if you pass along to the router a route object that matches the URI attached to the request, you should see the output (or whatever it does internally) generated by the corresponding action controller. The process seems to be fairly complex, sure, but if you look closer at the code samples, I’m pretty sure you’ll understand how the entire cycle flows. In either case, keep in mind that using such a granular schema, with several classes having just a limited, narrow set of responsibilities is entirely optional. If you just need to appeal to a simple -yet customizable front controller, the one discussed in the first installment does a pretty decent work, and can be easily hooked up to any standard MVC implementation.
I hope that helps you out.