The traditional answer would probably be CGI and (m)any of its derived modules (to manage sessions, authentication and authorization, ...), DBI and your choice of Templating System (Template::Toolkit springs to mind).
A more modern answer would be Catalyst and any related modules in that namespace to handle your particular challenge. Again a templating system (see above) and DBIx::Class if you need a database.
And I am probably forgetting a thousand other modules you cannot do without as my brethren will certainly point out!
CountZero
A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
In reply to Re: Perl, Web Apps, HTML::Template, HTML::Mason and the future
by CountZero
in thread Perl, Web Apps, HTML::Template, HTML::Mason and the future
by novastorm0
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |