connection pooling

[Cantor, Scott]

On 4/3/14, 10:14 AM, "Marvin Addison" <marvin.addison at gmail.com> wrote:
>
>May I recommend you consider tomcat-jdbc [1]. The simplicity of the
>code is refreshing, particularly compared to
>commons-dbcp/commons-pool. I've used it in a couple apps now and have
>been pleased with performance. I should note that it can be used
>independently of Tomcat; in fact we use it on Jetty with no hassles
>whatever.

I don't think the emphasis should be on us choosing anything, we should
ideally be consuming DataSource and leaving the rest to the deployer.

The only reason it matters right now is the custom schema's support for
some pooling options, so that pooling config has to map to something, but
I'm not sure it matters that much what it is, and compatibility may
dictate we just leave c3p0 in as a deprecated support feature when the
pooling settings are used and just tell people to stop using that syntax.
That's the path of least risk I suspect.

-- Scott