uzzikie has asked for the wisdom of the Perl Monks concerning the following question:
Fellow Monks,
i need some advice regarding the use of CGI::Application. Its more than a case of Scaling single-script CGI applications....
As stated in the synopsis, it is no doubt useful in creating sophisticated, reusable web-based applications. But what happens if i have hundreds of run-modes? Even though i can organize them neatly into different modules, what worries me is the overhead. Will CGI::Application attempt to load ALL the modules each time the script is accessed, even though they are not used? (now that's scary!)
Any thoughts and recommendations to handling such a situation?
i need some advice regarding the use of CGI::Application. Its more than a case of Scaling single-script CGI applications....
As stated in the synopsis, it is no doubt useful in creating sophisticated, reusable web-based applications. But what happens if i have hundreds of run-modes? Even though i can organize them neatly into different modules, what worries me is the overhead. Will CGI::Application attempt to load ALL the modules each time the script is accessed, even though they are not used? (now that's scary!)
Any thoughts and recommendations to handling such a situation?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Using CGI::Application in large projects
by crazyinsomniac (Prior) on Jan 22, 2003 at 09:55 UTC | |
Re: Using CGI::Application in large projects
by rob_au (Abbot) on Jan 22, 2003 at 09:50 UTC | |
by IlyaM (Parson) on Jan 22, 2003 at 15:49 UTC | |
Re: Using CGI::Application in large projects
by Ctrl-z (Friar) on Jan 22, 2003 at 13:57 UTC | |
Re: Using CGI::Application in large projects
by Ryszard (Priest) on Jan 23, 2003 at 08:46 UTC |
Back to
Seekers of Perl Wisdom