After introducing you to the subject of this series, I'd like to step back quickly to the previous tutorial and recall the topics covered in it. This will make it a bit easier for you to grasp the concepts that I plan to explain in this final part.

As you'll possibly remember, in the previous article I went through the development of a comprehensive error logging system. It used the chain of responsibility pattern to establish the scope of where each involved PHP class should act.

By following this approach, it was feasible to create an error handling mechanism where every component was initially provided with a limited capacity for processing a particular failure -- and when the error in question couldn't be properly handled, it would be immediately transferred to the corresponding parent module.

Indeed, if you reread the above paragraph, it should be clear to you what a chain of responsibility is all about: once a group of hierarchically organized classes have been created, the responsibility for handling a given task is moved from the bottom to the top of the stack structure. Sounds good, doesn't it?

Now, paying attention to the topics that will be covered in this tutorial, what you'll learn here will consist essentially of applying the chain of responsibility schema to expand the capacity of the error logging system that was developed  previously.

Are you intrigued about how this will done? Then click the link below and keep reading!