Mvc – Model-View-Controller (MVC) Which component handles save/load operations

Not entirely clear on what you are doing. But here is what I am assuming, you are writing some kind of application with large number of users updating same values(like price of a stock) and you want to use MVC on the client stack(JS) to create an desktop application like feel.

Having concurrency control in the controller seems right. If it was me I would write the controller as a bunch of classes(functions) with extensive support for call back. If there was successful, call this, if it failed call this.

Then in the View, Ill call the controller functions with right call back functions.

Even though this will work, I feel the architecture is too complicated. Either keep the server as a model only communication(acquire lock on edit, update on save, release lock on success) or move everything to server and use JQuery ajax to just do all the work.

A couple of things here:

• There are several ways of implementing MVC, each technology and kind of app has it. See this great article to have a better understanding.

• An action that involves only VC is not a violation, not every user action has to touch the three parts of MVC.

  1. The code that will add new text-fields will be controllers, which add a view (textfield) and should add a model representing what that textfield means in your app (if the view alone has any meaning then this VC-only relationship is ok).

  2. Changes in the view can come from two places: from the controller or from the model itself BUT by notifications (this means that the model must not know the views directly, but have a group of listeners that listens his changes).

I hope this answer plus the article clarifies a little bit more your knowledge of MVC and its implementation in your app.

Good luck!