Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
References: <55C69232.8070400@gmail.com>
In-Reply-To: <55C69232.8070400@gmail.com>
From: James Carman <james@carmanconsulting.com>
Date: Sun, 09 Aug 2015 00:04:40 +0000
Message-ID: 
 <CALznzY4o92EMxpNO1x_8RLwK41ozKbSQ9ux4CmQH-kGpOLAU9A@mail.gmail.com>
Subject: Re: [pool] Interceptors
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=047d7b414f2a24ab97051cd59e2a

--047d7b414f2a24ab97051cd59e2a
Content-Type: text/plain; charset=UTF-8

We talked about this a while back with respect to logging,, having a
PoolListener interface or something.

On Sat, Aug 8, 2015 at 7:36 PM Phil Steitz <phil.steitz@gmail.com> wrote:

> Tomcat's jdbc-pool has an interceptor feature that allows custom
> code to be inserted into methods called on connections managed by
> the pool.  In [pool], we have the core infrastructure to support
> this in a generic way via the ProxiedObjectPool.  I propose that we
> extend this to allow users to configure interceptors to be called
> when registered methods are invoked on checked out objects.  I
> haven't really thought through how configuration would work, but
> basically clients would register methods and possibly interceptor
> properties and the interceptors would get references to the method,
> arguments, pool and pooled object.  Configuring interceptors in a
> GOP or GKOP would cause it to be wrapped in a ProxiedObjectPool.
> Eventually, we could use this [pool] capability to enable the kind
> of thing that jdbc-pool provides with its interceptors in DBCP.
> With [pool] itself, I could see providing method stats collectors,
> abandoned timer reset (avoiding having to implement use()) and maybe
> a pooled object properties cache.   If there are no objections, I
> will open a JIRA and start experimenting.
>
> Phil
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

--047d7b414f2a24ab97051cd59e2a--