I think its simply a result of moving to a purely ajax driven UI. Eventually you only end up with calls to data stores.
Controllers should be dumb. Look up DCI as a way to augment MVC.
They also package data from various sources in a way that the view will understand. They also have to unwrap data from the view and feed it back to the model. This process can be quite complicate...
Yes. In things like this, one tends to have a store of models that's also a model. Sometimes recursively. An IDE has a store of projects, each of which stores a bunch of classes, each of which st...
Controllers do one thing, control which views you see. They are dumb.
But I think the idea is that, rather than being coupled to data structures, you build stores according to what is useful. You might have a FriendRelationStore which encapsulates mutual friendship...
> behaviorless models Annnnd.... there's the problem. What is being modeled if one's model has no behavior? That's not MVC. MVC assumes the model comes first and is independent of the views an...
> The models are responsible for enforcing the business logic - that's > what they're for. Right, but the controller is still doing the update--by calling the appropriate method on...
> updates of all the models it interacts with No, the update of one model should be triggering updates in other models. If the user is asked to add a friend, it should also tell the frie...
It seems that this architecture is shifting MVC to something that looks event-based. "Stores" register themselves (and presumably any call-order dependencies) with the dispatcher, and the dispatc...