Re: JNDI Datasource vs JDBC (Tomcat deployment)
Re: JNDI Datasource vs JDBC (Tomcat deployment)
- Subject: Re: JNDI Datasource vs JDBC (Tomcat deployment)
- From: Mike Schrag <email@hidden>
- Date: Wed, 12 Nov 2008 07:06:49 -0500
I think there was some talk here weeks ago (and something I had
wondered about a while back) about using an object store coordinator
pool. I think Mike brought it up -- Mike?
I don't recall this particular discussion (but then I talk a lot :) ),
but Wonder does have ERXObjectStoreCoordinatorPool. You tell it how
many stores you want and it will hand them out round-robin (well, a
little bit fancier than that, as it tries to keep a session on the
same pool, I think, and the current thread stays on the same pool).
Each store has its own db connection. The downside of this is that
you have multiple snapshot caches, so you potentially substantially
increase your memory footprint.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden