comment on

A good approach would be to write your code so that it can run under both plain CGI and mod_perl (or FastCGI or SpeedyCGI or PPerl for that matter).

Basically, this only means that you show some extra discipline concerning global variables, proper namespacing and such. Using a framework like CGI::Application takes you a long way here.

This way, you can have the extreme availability and ease-of-installation of pure CGI and if your site gets popular enough for performance issues to come into play, you can switch over to mod_perl. The code will continue to work (and be much faster, mainly due to eliminated startup time)

Making extensive use of mod_perl specific features (that would tie you into this architecture) is probably a lot of fun, but I do not think it is really worth the loss of flexibility.

In reply to Re: cgi or mod_perl by Thilosophy
in thread cgi or mod_perl by sberthold

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks