re: JNDI Datasource vs JDBC (Tomcat deployment)
re: JNDI Datasource vs JDBC (Tomcat deployment)
- Subject: re: JNDI Datasource vs JDBC (Tomcat deployment)
- From: Peter Newnam <email@hidden>
- Date: Thu, 13 Nov 2008 11:44:09 +1100
- Acceptlanguage: en-US
- Thread-topic: JNDI Datasource vs JDBC (Tomcat deployment)
>
> > 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
Thanks for the input Mike/Andrew.
Would that make multiple JDBC connections? Or is the intent of the design to improve multi threaded data retrieval from the EOF cache?
Once again a disclaimer - I am a WO newbie from a J2EE world :)
Peter
_______________________________________________
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