[Catalyst] ways to do stuff and why

[Kaare Rasmussen]

> There is one practical argument for having the business logic in the model
> - it is the necessity of using it from command line/cron job tools.  I have

But it's easily overcome if you put your logic in separate modules. I don't 
think that practical problems like this should dictate your design 
philosophy.

More than that, it seems to me that it's a major shortcoming of the MVC model 
that there's no real good place to put the real beef, the logic. i'd like to 
keep the model as a persistence layer. The logic I'd put there should only be 
concerned with keeping data consistent.
The controller should only be interested in moving things around and the 
viewer is completely out of the question :-)
So in my view, business logic, rules, computations (other than simple data 
twisting) and other stuff that has to be flexible doesn't really fit in. Of 
course you can have it in the model, but then the model really has two 
layers, a persistence and a processing layer.

Each developer has to solve that independently at least until Catalyst will 
shine as the first MLVC (Model-Logic-View-Controller) system ;-)

-- 

Med venlig hilsen
Kaare Rasmussen, Jasonic

Jasonic                 Telefon: +45 3816 2582
Nordre Fasanvej 12
2000 Frederiksberg      Email: kaare at jasonic.dk