InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

Hmmm, I stand corrected. That's what I get for not double-checking 
before I post :-( I could have sworn I learned that somewhere.

So why would you want to share a connection between threads? Do you need 
the threads to operate within the same transaction?

Scott

Peter Yuill wrote:

>> You should never have multiple threads accessing the same connection 
>> unless you're using some pooling mechanism that insures that two threads 
>> can't using a connection at the same time. This is true for any JDBC 
>> connection, not just InstantDB.
> 
> 
> Not so according to the spec. Section 9.2 says:
> "We require that all operations on all the java.sql objects be multi-thread safe and able to 
> cope correctly with having several threads simultaneously calling the same object"
> 
> If multi-threading is the problem (only speculation at this point) then its a bug.
> 
> Regards,
> Peter Yuill
> 
> -----------------------------------------------------------------------------
> To unsubscribe from this mailing list, send email to majordomo@enhydra.org
> with the text "unsubscribe instantdb" in the body of the email.
> If you have other questions regarding this mailing list, send email to
> the list admin at owner-instantdb@enhydra.org.
> 
> 

-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.