indigo has asked for the wisdom of the Perl Monks concerning the following question:
I am currently revising some HTML::Mason code. The original developer was not terribly familiar with CGI.pm, and wound up hand coding all the forms in raw HTML. This lead to really messy code and maintainability issues. I've made a pass through, and replaced all the form elements with CGI.pm calls.
The code is clean enough now, but it could be cleaner. In particular, the HTML leaves a something to be desired. I would like to go though and redo the table tags using CGI.pm, but I am concerned about performance.
I do not suspect 5 or 6 direct calls to the CGI form functions are going ot matter much. However, 40 calls through the autoloader to build a moderately complex table, that might be a little different.
Any wisdom on the performance of CGI.pm vs. straight HTML?
The code is clean enough now, but it could be cleaner. In particular, the HTML leaves a something to be desired. I would like to go though and redo the table tags using CGI.pm, but I am concerned about performance.
I do not suspect 5 or 6 direct calls to the CGI form functions are going ot matter much. However, 40 calls through the autoloader to build a moderately complex table, that might be a little different.
Any wisdom on the performance of CGI.pm vs. straight HTML?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: CGI.pm performance issues....
by damian1301 (Curate) on Mar 17, 2001 at 01:27 UTC | |
Re: CGI.pm performance issues....
by merlyn (Sage) on Mar 17, 2001 at 00:12 UTC | |
Re: CGI.pm performance issues....
by knobunc (Pilgrim) on Mar 17, 2001 at 00:02 UTC |
Back to
Seekers of Perl Wisdom