3 ms·
Sounds about right to me. Model in MVC isn't data model, it is a model of the application domain, aka business logic. The controller is supposed to map low le
by stonemetal 14y ago
Sounds about right to me. Model in MVC isn't data model, it is a model of the application domain, aka business logic. The controller is supposed to map low level input to high level model actions. The view goes the other way, high level model representation to low level operator display.
- jrgnsd 14y agoI think for a lot of people the Model is the DB layer. They then (rightfully) realize that you shouldn't combine business and DB logic, and then move their business logic into the Controller. So they're fixing a valid issue with an invalid solution, causing bloated and dual purpose (business and application logic) Controllers.