• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: JNDI Datasource vs JDBC (Tomcat deployment)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JNDI Datasource vs JDBC (Tomcat deployment)


  • Subject: Re: JNDI Datasource vs JDBC (Tomcat deployment)
  • From: Andrew Lindesay <email@hidden>
  • Date: Thu, 13 Nov 2008 13:52:05 +1300

Hello Peter;

Would that make multiple JDBC connections? Or is the intent of the design to improve multi threaded data retrieval from the EOF cache?

Each object store co-ordinator indirectly has its own set of JDBC connections -- a connection for each model.


cheers.

___
Andrew Lindesay
www.lindesay.co.nz

_______________________________________________
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


References: 
 >re: JNDI Datasource vs JDBC (Tomcat deployment) (From: Peter Newnam <email@hidden>)

  • Prev by Date: re: JNDI Datasource vs JDBC (Tomcat deployment)
  • Next by Date: Re: Frontbase CLOB newline problem
  • Previous by thread: re: JNDI Datasource vs JDBC (Tomcat deployment)
  • Next by thread: WebObjects binding to MYSQL Views
  • Index(es):
    • Date
    • Thread