Note that using cgi is not the same as using the CGI.pm module. The main difference between cgi and mod_perl is that for mod_perl the perl interpreter is embedded in the Apache process.
When writing/testing a web application, one advantage of cgi over mod_perl is that because cgi reloads your modules for each request, you can easily make changes without having to restart the server. mod_perl does have some tricks to get around that though.
The CGI.pm module helps make using cgi on a server easier, it can parse POST parameters, bake cookies, and generate compliant HTML code. With mod_perl some of that functionality is provided by the Apache:: modules, but you can use some parts of CGI.pm in mod_perl as well. So by all means, whether you use cgi or mod_perl, you should learn how to work with CGI.pm.
-
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.
|