Don't ask to ask, just ask | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Where that code belongs to? Probably into the model. The model should be a collection of routines and/or classes which do your "business logic", ie do the actual work behind the scene. If you don't know whether a piece of code belongs to the controller or to model, imagine that you write another program which offers the same functionality, but a command line (or GUI) interface instead of a web frontend. Would that alternative program also benefit from the piece of code you're currently writing? If yes, it belongs to the model. An Included file seems to be very ugly, or not? There's nothing wrong with useing the modules you need. Mostly it is procedural logic. But I imagine that a good idea should be create something like a "subcontroller" named Person, almost like a Class. We don't know enough about your problem to know if that's a good idea or not. There's no inherent advantage of object oriented interfaces over procedural interfaces. In reply to Re: I need wisdom on structuring procedural code in Catalyst
by moritz
|
|