Symfony2 is a reusable set of standalone, decoupled, and cohesive PHP

components that solve common web development problems.

Before we dive into the code refactoring, I first want to step back and take a

look at why you would like to use a framework instead of keeping your

Up until now, our application is simplistic as there is only one page. To

spice things up a little bit, let's go crazy and add another page that says

Before we start with today's topic, let's refactor our current framework just

a little to make templates even more readable::

The astute reader has noticed that our framework hardcodes the way specific

"code" (the templates) is run. For simple pages like the ones we have created

Create your own framework... on top oftheSymfony2 Components (part 6)

The HttpKernel Component:theController Resolver

You might think that our framework is already pretty solid and you are

probably right. But let's see how we can improve it nonetheless.

Create your own framework... on topofthe Symfony2 Components (part 7)

The SeparationofConcerns

One down-side of our framework right now is that we need to copy and paste the

code in ``front.php`` each time we create a new website. 40 lines of code is

Some watchful readers pointed out some subtle but nonetheless important bugs

in the framework we have built yesterday. When creating a framework, you must

Our framework is still missing a major characteristic of any good framework:

*extensibility*. Being extensible means that the developer should be able to

In the conclusion of the second part of this series, I've talked about one

great benefit of using the Symfony2 components: the *interoperability* between

If you were to use our framework right now, you would probably have to add

support for custom error messages. Right now, we have 404 and 500 error

In the last installment of this series, we have emptied the

``Simplex\\Framework`` class by extending the ``HttpKernel`` class from