In an MVC pattern, who handles requests to the view? Does the controller act as the router sending function calls to either the view or the model, or is it more common to call functions right on the view?

I guess another option would be to inject listeners on the view and then call them, for loosely-coupled environments, but I don't know if that's just overkill.

Thanks for any advice