Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: 207.173.203.201 is neither permitted
 nor denied by domain of david@kineticode.com)
Subject: Re: How do you use mod_perl for your web application?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "David E. Wheeler" <david@kineticode.com>
In-Reply-To: <F2BD5EBC20F9467A80355E718E119D66@teddy>
Date: Mon, 27 Jun 2011 13:10:25 -0700
Cc: "Fred Moyer" <fred@redhotpenguin.com>,
 <randolf@modperl.pl>,
 "mod_perl list" <modperl@perl.apache.org>
Content-Transfer-Encoding: 7bit
Message-Id: <F7DDD618-BB11-45B1-9E97-FBAB013B9E12@kineticode.com>
References: 
 <BANLkTim2Lwhbr=Q_nsJxH0jmwgZweoA6uA@mail.gmail.com><BANLkTi=obm39jCzo9NW5U2A7_4YzddpQrw@mail.gmail.com><BANLkTikH1HwCsdaiBkirO24HQOc1D0akYg@mail.gmail.com><4E07CA98.29249.1B161F@randolf.modperl.pl><5886A750117D4EA9B9AD015BB89131FD@octavian>
 <BANLkTi=VBgs6AbmocjyQ=E8geXbUqBtpjg@mail.gmail.com>
 <F2BD5EBC20F9467A80355E718E119D66@teddy>
To: Octavian Rasnita <orasnita@gmail.com>

On Jun 27, 2011, at 12:53 PM, Octavian Rasnita wrote:

> DBIx::Class already manages its connections for you, and therefore it
> cannot benefit from Apache::DBI under any scenario.  It makes one
> connection per-process, and keeps that connection persistent,
> reconnecting only if the connection appears to have died, or if you
> fork/thread over to another process/thread-id.  The only Apache::DBI
> issue in DBIx::Class is that Apache::DBI will actually thwart
> DBIx::Class's connection management code, and cause it to use the same
> (and invalid) connection in a new process, in cases such as (as
> mentioned above) if you make a DBI connection before forking in a
> prefork mod_perl server.
> 
> To work around this, DBIx::Class has specific code in it to work
> around Apache::DBI, nullifying the effects of Apache::DBI on
> DBIx::Class.  Essentially, loading Apache::DBI should change nothing
> and be rather pointless under DBIx::Class.
> 
> The only reason we support it (support working around it) is because
> someone might want Apache::DBI loaded up under the same mod_perl as a
> DBIx::Class application to support a different legacy application
> which does not use DBIx::Class, in which case they share a perl
> interpreter and will both have the same set of modules loaded.

The same statements apply to DBIx::Connector, FWIW.

Best,

David