-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jukka,
On 2/28/13 4:25 PM, Christopher Schultz wrote: > On 2/25/13 12:52 AM, Jukka Ruohonen wrote: >> A question related to pools. Background: a big application in >> which it is preferable to enforce different roles for different >> databases and tables. This implies that there are different user >> names and passwords for different connections. As I understand, >> there are two options for connection pooling in a scheme like >> this: > >> A. Create different resources for the different roles, each >> having the user names and passwords defined as constants in the >> Tomcat configuration files. > >> B. Group the different roles into a bigger scheme and use the >> option 'alternateUsernameAllowed' to obtain the connections with >> the specific user names and passwords. > > C. I believe that tomcat-pool (*not* the stock one based upon > commons DBCP) supports the DataSource.getConnection(username, > password) call and might even be smart enough to search-through > existing connections for one that matches those credentials. > > This will allow you to have a single DataSource but still have > different credentials for your connection on-demand. Sorry, I forgot to mention how this is different from (B): you can use as many usernames and passwords as you'd like. The downside, obviously, is that you might have a lot of turnover (i.e. thrashing) in your connection pool. But if that's essentially what your requirements are, there's nothing you can do to minimize that problem. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEAREIAAYFAlEv9+gACgkQ9CaO5/Lv0PCKEQCfYO5TkkXm6gQFgqjU2hP1hMWG S7oAoIyIWufo46+ygL3wPbK7h9lNevhl =L5XQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
