Hi jessie,
Think it can makes sense but not sure it fits in commons-dbcp "core" since
the best is generally to not merge the connection in the same pool but use
N pools and enable the database to inject a custom "router"/selector
(that's what spring or tomee did for ex [1]/[2]).
The rational to
+1
On Wed, Nov 8, 2023, 7:24 PM sebb wrote:
> I would really like to drop support for the oldest versions of SSL, i.e.
> 1.0.x
> These are seriously out of date.
> Can we even test them properly?
>
> Unless I hear otherwise, I propose to remove the code next week.
>
> Sebb
> On Mon, 30 Oct 2023
I would really like to drop support for the oldest versions of SSL, i.e. 1.0.x
These are seriously out of date.
Can we even test them properly?
Unless I hear otherwise, I propose to remove the code next week.
Sebb
On Mon, 30 Oct 2023 at 14:33, sebb wrote:
>
> On Mon, 30 Oct 2023 at 12:31, Gary
Crypto now builds and tests OK on
macOS-latest - OpenSSL 3.1.4 24 Oct 2023
and
Ubuntu-latest - OpenSSL 3.0.2 15 Mar 2022
Tested with Java 8 and 21
I only had to allow for two changed names:
EVP_CIPHER_CTX_block_size => EVP_CIPHER_CTX_get_block_size
EVP_CIPHER_flags => EVP_CIPHER_get_flags
This
Hi Jesse,
Please take a look at Commons DBCP and how your proposal would fit in.
Gary
On Wed, Nov 8, 2023, 4:49 PM Jesse Harris
wrote:
> Would there be any interest in contributing an implementation of a multi
> tenant connection pool implementation?
>
> One implementation of a multi-tenant
Would there be any interest in contributing an implementation of a multi
tenant connection pool implementation?
One implementation of a multi-tenant architecture is to have a schema per
tenant, the downside is that you need to set the default database on each
connection pulled from the pool, this
