MVC is such an overloaded term ... I don't think I've seen behavioral equivalence between any two implementations/frameworks in any language I've dealt with. As

MVC is such an overloaded term ... I don't think I've seen behavioral equivalence between any two implementations/frameworks in any language I've dealt with. As always, the devil is in the details. So going much further than "the model deals with data (either connected or unconnected), the controller usually deals with behavior, and the view usually deals with presentation" it's really hard to talk about MVC in general without some tighter constraints. For instance, are you models POJOs? Are they tied to the DB directly (i.e. something like ActiveRecord)? Do they process/send events (i.e. something like a model in Swing)? Etc ... It get's complicated fast if you want to discuss more than very abstract generalities.