Hello team,

we have to use tdb in a setting where we cannot follow the "one transaction per 
thread" idiom because the threads are not under our control. So, according to 
the docu statement

(*) "Applications needing to do so must ensure that only one thread starts the 
transaction, via a Dataset object, and that all threads are acting 'multiple 
reader OR single writer'"

we have one global transaction object T, which is started in only one thread, 
and share T between thread t-1 to t-n.
We also ensure that only one thread t-i can be a writer. Is this enougth, i.e., 
have I interpreted the docu in the right way ???

thanks in advance, Andreas

Reply via email to