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.
Here you have to decide wether you will keep the connection or not, and if
it something happens, like closing, you have to wait until user hits the
page. Yes you can make ModPerl timestamp DBI links, so that they can be
timed out next time a user calls one of the DBI functions, maybe connect?
But asynchrosity is out of the question. It would be cool however if you
can insert your socket into apaches select queue... isn't that how it
works? Then you can really do some funky stuff...
just 2c
Pavel
