On Oct 2, 2009, at 9:30 AM, Kurt Hansen wrote:
I'm wondering what techniques folks are using to get persistent
database connections other than Apache::DBI.
I plan to release a new module, DBIx::Connection, on Monday. It's
based on the connection caching stuff in DBIx::Class, and also has
On Oct 2, 2009, at 3:25 PM, Perrin Harkins wrote:
On Fri, Oct 2, 2009 at 5:54 PM, Jonathan Swartz
wrote:
Ok, one more question. Disregarding graceful for the moment - is HUP
completely reliable with mod_perl at this point, or is there still
a reason
(as there once supposedly was) to do a
On Fri, Oct 2, 2009 at 5:54 PM, Jonathan Swartz wrote:
> Ok, one more question. Disregarding graceful for the moment - is HUP
> completely reliable with mod_perl at this point, or is there still a reason
> (as there once supposedly was) to do a full server stop and start?
The problem, at least in
On Sep 25, 2009, at 10:48 AM, Clinton Gormley wrote:
If I don't ever plan to use graceful restarts, and I believe that
smaller restart times are an unqualified Good, is there any reason
why
I shouldn't ALWAYS use a script like the above? And is there any way
to avoid PerlModule modules from
Apache::DBI is fine. You can also use DBI->connect_cached, as long as
you are careful to avoid making any database connections during server
startup and install your own cleanup handler to issue a rollback on
all open database handles at the end of every web request.
The Apache::DBI code is very
I run 1.07 on my webserver (algebra.com) and Apache::DBI works great for me.
i
On Fri, Oct 2, 2009 at 11:30 AM, Kurt Hansen wrote:
> Hello,
>
> I'm wondering what techniques folks are using to get persistent database
> connections other than Apache::DBI.
>
> Apache::DBI has worked great, but I'
Hello,
I'm wondering what techniques folks are using to get persistent database
connections other than Apache::DBI.
Apache::DBI has worked great, but I've treated it as a black box and so
don't fully understand what it is doing in the box. That was fine, but
the fact that the current version
Hello,
The problem I'm trying to solve is that a page request will have to
look for data from two sources: local & external. What I would like to
do is put the external lookup (which is slow) in it's own thread and
do the local processing as far as I can while waiting for the external
source. Then
Douglas wrote:
I want to add the session id to the access log entries.
We just added "%{session_id}C" as an additional field to
our CustomLog directive, and that worked fine for us.
http://httpd.apache.org/docs/2.0/mod/mod_log_config.html
--
Cosimo
