You're almost there...
Putting the REST between the view and the controller would be the right choice. That means that your view, i.e. a
REST calls to your server, which process those calls in the appropriate controller (then the models and etc.). In addition this controller would be responsible for the
response back to the client.
I believe you have a confusion with the controller's part in the system. Depending on your implementation and application frameworks you're using, the controller should be part of your 'server' layer, which tells which and what view to call/dispatch.
Take a look at the following (simple) diagram:
The controller is responsible for updating the view, and maybe showing you another view.
For example, consider the following scenario:
- The user fills out a form and submits it
Server validates the form and
2.1. If it is valid - the controller will route you to a "thank you" view
2.2. else the controller will route you to a "missing input" view
- The user gets the routed view as a response.