----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Les Mikesell" <[EMAIL PROTECTED]>
Cc: "Tim Bunce" <[EMAIL PROTECTED]>; "Aaron" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, November 15, 2000 2:21 AM
Subject: Re: database access
> On Tue, 14 Nov 2000, Les Mikesell wrote:
>
> > I wonder if Apache::DBI could figure out what connections are worth
> > holding open by itself? It could have some hints in the config file
> > like regexps to match plus a setting that would tell it not to
> > make a connection persist unless it had seen x instances of that
> > connect string in y seconds.
>
> That really, really sucks, but Apache is selecting on the HTTP socket, and
> nothing matters beyond that, except signals of course. What you are
> implying is that DBI will be aware of the connections being closed or
> SIGALRM coming thru to the apache and on its lap, but it won't happen.
No, I realize there is nothing to do after the fact - what I meant was that
Apache::DBI might allow disconnect to really happen the first few
times it sees a connect string after a child startup. If it saved the
string with a timestamp and waited until it had seen the same string
several times within a short interval it would be fairly likely that it
would be worth staying connected. You'd trade some slower hits
off against not accumulating a huge number of little-used database
connections.
Les Mikesell
[EMAIL PROTECTED]
