[Catalyst] Re: Controllers vs Models

[Justin Tocci]

I'm not sure what you're saying here.

Closer to me or David?
Is '"domain" knowledge' referring to business logic or flow control  
or something else?

I agree that flow control is necessitated by the web in a way that  
was unnecessary for desktop apps. However, in a simple desktop app,  
flow control is often left up to the user. They get a menu and can go  
where they wish. But more complex apps have always said they need to  
log in first, etc... Hmm, ok, this would be business logic more than  
flow control too I think.

Ah-hem. I agree that flow control is necessitated by the web in a way  
that was unnecessary for desktop apps. ;-)

By the way, what was the Model before it was "just a set of database  
access objects"?

justin



On Jun 6, 2005, at 12:13 PM, Perrin Harkins wrote:

> On Mon, 2005-06-06 at 12:15 -0400, David Storrs wrote:
>
>>> I disagree. I think the controller should control program flow in a
>>> generic way, and that business logic is best factored out of it.
>>>
>>
>> Well, two thoughts here.  First, I was talking about how the MVC
>> pattern is usually presented in the literature.  I believe you are
>> talking about how you think the MVC pattern /should/ work.
>>
>
> Maybe we're just reading different literature, but I've usually  
> seen MVC
> described closer to the way he's talking about it, i.e. the controller
> is a totally generic mechanism for turning mouse clicks into method
> calls, and contains no "domain" knowledge at all.  The idea that the
> model is just a set of database access objects and that flow control
> goes in the controller is a relatively recent change stemming from the
> use in web apps.
>
> - Perrin
>
>
>