Phlip wrote: > Railsters: > > I heard a rumor that the incorrect answer, "Controller", was in circulation > out > there.
That's how I was taught MVC, long before I'd heard of Ruby: Models do some basic checking, but business logic belongs in the controller. That was the point of the controller; it gave a central place to put business logic. > The C should be as thin as possible, like a telephone patch-board. The View > should be thick, but only with Viewey things. That's the Rails take. Rails munges terminology a little. Rails models do a lot of what used to be done by controllers. I'm not saying it's a bad thing, but MVC far predates Ruby, and supposed "best practices" change over time. > The Model should be as fat as possible. Anything a user can do to the biz > rules, > thru the View, unit test can do to the Model directly. That's not necessarily true. > So the question is: Where did this disinformation come from? Do any websites > (or > >cough< books) out there actually say the biz rules belong in the controller? I first used MVC with MFC, about 10+ years ago, and in Java shortly thereafter. Fat controllers may have been advocated by MS back then. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
