It's fairly simple if you look at it. Mod_Perl and Mod_PHP have basically nothing in common. Basically mod_php is simply Apache::Registry, or possibly even less. It simply embeds the php interpreter in apache so it doesn't have to start it up for each script it calls. Mod_Perl on the other hand allows you to write complete modules for apache. It's commonly mentioned as simply away to speed up perl scripts, which is where this commmon misconception comes from, but thats nothing compared to the true power of mod_perl. It basically lets you rewrite any part of the apache request model you want, just like any of the other apache modules. Which is why real mod_perl hosting is more expensive, because you basically have to provide one apache server per person who wants mod perl, as anyone running mod_perl scripts has to have access to configuration file for the entire server, and theres no way to 'cordon off' various mod_perl scripts from each other.
Now what a hosting provider could do fairly easily is just set up Apache::Registry for each of it's clients in a certain directory,(and I think a few of them do this..) but that is nothing like mod_perl, it just a simple hack to speed up scripts.
-
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.
|
