Provide clean memory on each request, so that dirty CGI scripts would also run I think that is just what makes mod_perl so fast and mod_cgi so slow. Because you don't have to reload/re-compile the scripts every request, you get the speed-up. I do not know of a way to keep the compiled code around (other than turning it into an *.exe file) after having it run but still provide a clean slate of variables and state each time it runs again. It's an interesting idea though and perhaps worthwhile of further research.
CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
-
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.
|