Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have an articles and a notifications table. Whenever an article is successfully saved in the database, I send a notification to the user about it from within the model.
My question is…
Is it permissible in the MVC design to do this or should I use controllers for what I’m doing.
Absolutely, and you should probably not use a controller for this unless it is exclusively triggered by a request, or dependent on request parameters. In most cases, this is business logic that belongs in the model layer.
Alternatively, you could take a look at observers if you want to keep the actions of saving the article and notifying the user decoupled from each other.