Hello,
I'd like to ask what is the intended behaviour of
Apache2::ServerUtil->server->push_handlers(PerlCleanupHandler => ...)
compared to
Apache2::RequestUtil->request->push_handlers(PerlCleanupHandler => ...)
On my Ubuntu 8.10 (mod_perl 2.0.4, apache 2.2.9) cleanup handlers
installed on $s se
Hi.
Without being an expert, this is my 2 cent :
Kostas Chatzikokolakis wrote:
Hello,
I'd like to ask what is the intended behaviour of
Apache2::ServerUtil->server->push_handlers(PerlCleanupHandler => ...)
compared to
Apache2::RequestUtil->request->push_handlers(PerlCleanupHandler => ...)
O
On Fri 05 Dec 2008, Kostas Chatzikokolakis wrote:
> I'd like to ask what is the intended behaviour of
> Apache2::ServerUtil->server->push_handlers(PerlCleanupHandler =>
> ...) compared to
> Apache2::RequestUtil->request->push_handlers(PerlCleanupHandler =>
> ...)
>
> On my Ubuntu 8.10 (mod_perl 2
Thanks for the quick and prompt reply guys.
> $s->push_handlers as well as $s->add_config modify the server
> configuration object while $r->... modify the runtime request
> configuration. The server methods are intended to be used only at
> startup time (up to PerlPostConfig, perhaps PerlChild
Hi
The mySQL documentation for LAST_INSERT_ID says that it returns the last
auto-incremented field value for 'that client'.
I am not sure what the client is in a mod_perl situation with Apache::DBI?
I have an Apache child process which uses one open database connection for its
lifetime. If 2 p
On Fri, Dec 5, 2008 at 5:39 PM, Justin Wyllie <[EMAIL PROTECTED]> wrote:
> The mySQL documentation for LAST_INSERT_ID says that it returns the last
> auto-incremented field value for 'that client'.
>
> I am not sure what the client is in a mod_perl situation with Apache::DBI?
The current connectio
