[Catalyst] mapping application flow into a MVC framework (long)

David Storrs dstorrs at dstorrs.com
Mon Jul 11 20:58:54 CEST 2005

On Jul 11, 2005, at 2:02 PM, Phil Mitchell wrote:

> Just a guess, but it sounds to me like you may have too much code in
> your C classes. The way I think about it is that the controllers are
> for managing the request/response/validation cycle, and all the
> domain-specific stuff (related to servers, customers, etc.) should get
> pushed back to your M classes. Your C asks the model for a list of
> servers, the model gives back the right list, and C hands it off to
> the V for display.
> I know there was a discussion of MVC a while back on this list, which
> came to a different conclusion. I'm curious if people strongly
> disagree with the above...

I remember the discussion you mention.  My takeaway from that  
discussion was as follows:

Full consensus on:
- The M accesses the backing store (usually an RDBMS)
- The C handles request/response/validation
- The V displays things
- The domain logic does NOT go in the V

The discussion centered around whether to put the domain logic in the  
M or the V.  There are good arguments for it both ways, and I think  
it's something of a matter of taste--or, more specifically, a matter  
of your internal metaphor for the various components.  It'll work  
either way, so it's probably best to choose what fits your brain and  
then run with it.


More information about the Catalyst mailing list