httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matus UHLAR - fantomas <>
Subject Re: [users@httpd] Difference in mod_perl & mod_php
Date Wed, 04 Jun 2008 06:30:31 GMT
> From: "howard chen" <>
> >On Wed, Jun 4, 2008 at 1:16 AM, Joshua Slive <> wrote:
> >>On Tue, Jun 3, 2008 at 1:09 PM, howard chen <> wrote:
> >>
> >>Yes, if by "embedded" you mean "running in the same process/thread
> >>space with direct access to the apache API".
> >>
> >>Joshua.
> >
> >The difference is, say using mod_perl, modules are long live as long
> >as Apache is running and global variables can be shared across request
> >from different clients.

On 03.06.08 21:31, Octavian Rasnita wrote:
> Yes, and for this reason, in a mod_perl program you could create a 
> permanent connection to the database and each time you make another query, 
> you don't need to establish a new connection, and this means that it will 
> work faster.

mod_php supports permanent connections to databases too. At least to mysql.

The biggest problem with mod_perl is that people tent to compare it with
mod_php. They could compare it with mod_rewrite, mod_log_common, or mod_proxy
with similar results (differences).

mod_perl can do (nearly) anything what any modules can do. It will be just
done by perl interpreter, instead of interpreting binary code compiled from
C (as most apache modules are) by CPU itself.

Matus UHLAR - fantomas, ;
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Boost your system's speed by 500% - DEL C:\WINDOWS\*.*

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message