Hi List! I'm a new-ish Catalyst developer, converted from the ranks of the HTML::Mason faithful, and the recent nature of my dedication to MVC design, and to Catalyst's fat-model pattern specifically, has left me with some questions that I hope you folks can help me with. I'm trying to understand how I would go about moving my application's business logic, which seemed at first glance to fit quite logically into Catalyst's Controllers, into the Model. Specifically, in this case I've got a Catalyst::Model::DBIC::Schema model to obtain my application's data from; should I try to implement my business logic in that model (and if so, where? In the DBIC model PM? In the schema definitions?), or should I create a separate 'application object' model which brokers requests from the Controllers and uses the DBIC model to implement them if they fit the application's logic? I've looked far and wide to try to better understand how this pattern should work, since I can see the benefit of the better code reuse and easier maintenance it would entail; I just need some advice to get me started. Suggestions?
Cheers, Jeff Albert [email protected]<mailto:[email protected]>
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
