No, I think the reasoning is that a model is "This is how my business logic works", and a controller is "This is what the outside world is allowed to requests of my models".
On Sep 3, 3:09 pm, Aldric Giacomoni <[email protected]> wrote: > I've read this a few times recently. > I thought a model's job was only to explain "This is how I behave > myself" and the controller's job was to explain "This is what I do". > Is this basically right? So why do people want to stuff more and more > stuff in the model? > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
