By: Allex Gervasio

Hey Les,
Thanks for the kind comments. In a wider view, the dispatcher is actually responsible for encapsulating the instantiation of the page controller, only that in this case the task is performed through an external collaborator, namely the matched route. Of course, there’s plenty of room to experiment here (.i.e. provide the dispatcher with a factory method that “really” creates the appropriate controller using the data packaged in a route struct). Indeed the options to play around are rich and plethoric, as long as you keep each component performing a few discrete tasks within a typical request/route/dispatch/response cycle.