has the digest software for the mod_perl list changed recently? Here's a
sample of what I've been seeing for a couple of weeks at the top of the
digest:
cheers
andrew
Topics (messages 11320 through 11349):
(null)
113
heers
Andrew Dunstan
Senior Software Engineer
AnyDevice
Title: Software Developer
Start Date: ASAP
Job Description: Supporting the ASP model, this person would be responsible
for remodeling web content for a variety of wireless devices.
Req
heers
Andrew Dunstan
Senior Software Engineer
AnyDevice
Title: Software Developer
Start Date: ASAP
Job Description: Supporting the ASP model, this person would be responsible
for remodeling web content for a variety of wireless devices.
Req
Regarding cost of forking etc.:
Your mileage will undoubtedly vary, according to OS and MTA.
Last time I did work on this was about a year ago on Solaris
2.6, with sendmail and postfix. In both cases using Net::SMTP
was far faster. IIRC, with postfix there is no forking cost at all,
Could someone please explain to me why everybody seems so intent on having a mod_perl
handler fork in order to send mail? Why not just use the very common Net::SMTP package
which just talks on an SMTP socket to whatever mailhost you have (localhost or other).
There are other packages on CPAN
The DBI manpage says this:
connect_cached is like connect, except that the database handle returned is
also stored in a hash associated with the given parameters. If another call
is made to connect_cached with the same parameter values, then the
corresponding cached $dbh will be returned if it i
All these tips and benchmarks on optimising mod_perl by preloading used
modules/DBD-drivers etc. are great. However, I have seen warnings about
preloading modules if mod_perl is loaded as a DSO. (e.g for
HTML::Embperl). Does this still apply? My setup is
redhat6.2/perl-5.6/mod_perl-1.23.
TIA
And
