At 03:36 AM 11/14/2002, James Ponder wrote:
>On Wed, Nov 13, 2002 at 08:43:05PM -0500, Jeff Trawick wrote:
>> The recommended approach is to register a cleanup with the conn_rec
>> pool. When the connection goes away, so does the conn_rec pool, and
>> your cleanup will then run.
>
>Does that place
James Ponder <[EMAIL PROTECTED]> writes:
> On Wed, Nov 13, 2002 at 08:43:05PM -0500, Jeff Trawick wrote:
> > The recommended approach is to register a cleanup with the conn_rec
> > pool. When the connection goes away, so does the conn_rec pool, and
> > your cleanup will then run.
>
> Does that p
On Wed, Nov 13, 2002 at 08:43:05PM -0500, Jeff Trawick wrote:
> The recommended approach is to register a cleanup with the conn_rec
> pool. When the connection goes away, so does the conn_rec pool, and
> your cleanup will then run.
Does that place any restrictions on what can be done in the clean
James Ponder <[EMAIL PROTECTED]> writes:
> I would like to be able to monitor connection establishment
> (pre_connection) and connection termination (post_connection), however
> only the former hook exists. I was thinking the best way would be to modify
> ap_process_connection in connection.c to
Hi.
I would like to be able to monitor connection establishment
(pre_connection) and connection termination (post_connection), however
only the former hook exists. I was thinking the best way would be to modify
ap_process_connection in connection.c to add the post_connection hook, as
below:
AP_C
