[Catalyst] ways to do stuff and why
zzbbyy at gmail.com
Tue Aug 22 10:17:36 CEST 2006
If I reformulate my statement as follow:
There is one practical argument not to have the business logic in the
controller - it is ...
Can we agree?
The result I would like to get from this conversation is that I don't see
some point of time controllers with business logic in them at CPAN.
On 8/22/06, Kaare Rasmussen <kaare at jasonic.dk> wrote:
> > There is one practical argument for having the business logic in the
> > - it is the necessity of using it from command line/cron job tools. I
> But it's easily overcome if you put your logic in separate modules. I
> think that practical problems like this should dictate your design
> More than that, it seems to me that it's a major shortcoming of the MVC
> that there's no real good place to put the real beef, the logic. i'd like
> keep the model as a persistence layer. The logic I'd put there should only
> 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.
> 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
> 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
> List: Catalyst at lists.rawmode.org
> Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
> Searchable archive:
> Dev site: http://dev.catalyst.perl.org/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalyst