There could be a Router.create_controller method that gets called from BaseApplication.create_controller and then Router can internalize all the controller info stuff. A pro would be all that stuff is in one place, a con would be Router would now have to know about Request and Response, or just Request if it didn't want to create an actual controller instance.
There could be a
Router.create_controllermethod that gets called fromBaseApplication.create_controllerand then Router can internalize all the controller info stuff. A pro would be all that stuff is in one place, a con would be Router would now have to know about Request and Response, or just Request if it didn't want to create an actual controller instance.