in reply to Is there a standardized directory structure for perl applications
In general, you want to structure your modules so that related code is in the same, or related modules, and unrelated code is separated into other modules. For instance, you may want to have "generic" HTML generating / templating code in one module, and have database-access code in another. Once you do that, you should also take a look at CPAN, since there are many many modules there that help you with these subproblems.
Also see this article I wrote on MVC for the web - at least as a short introduction to a common way of separating concerns in web apps.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Is there a standardized directory structure for perl applications
by actualize (Monk) on Jul 17, 2008 at 22:29 UTC |