|
Richard, Couldn't they just call the getter and setter to mess things up? David Morris >>> cujo@us.ibm.com 04/09/02 11:44AM >>> ...But later, we start seeing heavily threaded applications, applications sharing transactions (via JTA support sitting on top of JDBC), etc. So we synchronize everything in connection and synchronized everything in statement to stop two threads from messing up a single object, but the problem that remained was that threads doing stuff to the statement are 'free' to modify the connection because they didn't call a method on the connection, they just changed what they wanted to. This caused some inconsistancies that were very hard to track down... Richard D. Dettinger iSeries Java Data Access Team
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
