Re^2: mod_perl website structure

[Anonymous Monk]

Nothing wrong really , but a common strategy is to seperate concerns, which you've done by using functions , but you could seperate them out a bit further, by means of model view controller pattern, which becomes more important the bigger your project becomes

More things to read (start with the pm links)

• pm The Model View Controller pattern in web applications
• MVC Pattern
• bingo http://www.aspiringcraftsman.com/2007/08/25/interactive-application-architecture/
• pm Re: Seeking MVC Wisdom
• mod_perl: Choosing a Templating System
• http://suryahunter.com/wiki/hunter/perl_ironman/mount_multiple_apps_with_plack
• regarding PSGI/Plack versus mod_perl or CGI PlebGUI: WebGUI Meets Plack » patspam
• tired of writing meta code in templating languages ? HTML::Seamstress
• good point regarding RESTfulness http://web.archive.org/web/20110720174434/http://www.dehora.net/journal/2007/08/web_resource_mapping_criteria_for_frameworks.html
• CGI::Prototype
• http://www.simon-cozens.org/content/i-finally-get-psgi-and-plack

If your application isn't tied to a particular implementation (mod_perl), if you target PSGI/Plack, you can run on mod_perl or practically any webserver