If you're relatively new to the world of the MVC (Model-View-Controller) design pattern and its use, you may be trying to figure out exactly what each piece is. One of the more difficult relationships is between models and controllers, more specifically what each are supposed to contain. In this discussion over on Reddit several people weigh in on their opinions and own suggestions about what models should be.
Sometimes I feel I should avoid session in model ... but sometimes I feel using session in controller is putting business logic in controller which is bad ... sometimes I feel I should avoid $_POST and $_GET in model ... but sometimes I feel receiving data in controller and then send all of them to model is an unnecessary move ... sometimes I feel one model should represent almost everything about one certain table ... sometimes I feel it's almost god pattern if that table is the core of your application, but separate the model into many model is confusing too since they are using the same table. I wanna be a Model Master who can explain 'Model' very well. Who can help me plz.
Comments on the post explain models in several different ways including:
- Thinking of it as a representation of "domain" functionality
- Models as a 1-to-1 relationship with database tables
- The differences between them and collections
- Links to some helpful libraries like Eloquent and Doctrine
Link: http://www.reddit.com/r/PHP/comments/28luto/what_exactly_is_model_in_mvc/
没有评论:
发表评论