I think that also the Fat Model aspect doesn't really need to mean that any one model is particularly big, just that it is where the logic should go instead of in the controller. It could be a number of small focused classes rather than a few big ones ... just not controllers. On Wednesday, 23 February 2011 at 7:26 PM, jamesl wrote: > We all know Rails is great and the community is very supportive. > However, there are some practices that leave me a little puzzled/ > bamboozled. > > The Skinny Controller, Fat Model post by Jamis Buck (http:// > weblog.jamisbuck.org/2006/10/18/skinny-controller-fat-model) appears > quite popular. It was referenced in several conversations I have had > and in the PragPub RSpec book. > > But why is the practice of a Fat Model more acceptable than a Fat > Controller? > > I think a Skinny Controller is great but I also think a Skinny Model > is great too . > I want to know if others keep their Models Skinny and if so how? > > BTW - to keep the model skinny I don't mix the concerns of Business > with that of an Entity (See Domain Driven Design - Eric Evans) > > Rgs, James. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" 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/rails-oceania?hl=en. >
-- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
