RE: Should controllers be "smart"?


Model-View-Controller architecture wants you to put your business logic
into the controller.


One of the things that DHH always talks about is having a rich domain
model. This is why we have stuff like validations, associations, etc
all being inside the model.

I’ve actually never really understood the point of the controller.
Everywhere I’ve read says that the business logic goes in the model,
and the controller just connects it to the view. Maybe I’m just

If business logic goes in the controller, how are you supposed to
modify the application other than by using a web interface?


This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs