Originally Posted by asabi

Well, I now understand the way forward works, it just changes the request parameters to point to the next controller.

What I really look for, is a way to do a 'sub' request, something along the lines of creating a new request, to another controller, dispatch it, and use the result inside the current controller.

I see a need for it for anything that needs to be repeated in multiple pages, like navigation for example.

So, instead of creating another view inside the controller, and render it, why not just call another controller action, which already creates the view, has all of the model calls and the call to render ...

I guess everything is a singleton when it comes to the front controller and the request object.

Again, do I have anything wrong in my thinking ?