|I'm pretty sure that the above is something that is not allowed, i.e.
|forking threads does not mean that the tx is in the forked thread as well.

without the forking, which i think is perfectly valid, you tend to think of
the transaction in a "reductive" way.. the transaction is something larger,
many clients can participate in a transaction and their scheduling is not "a
priori" (like implicitely if you only have your "logical thread")

|My case still holds IMO: there is only one logical thread of execution per
|transaction.

YHO is not going to cut it... show me the law, and I am not even sure what
it means... how are you going to go from one thread to the other, what does
your "logical thread" use to do that?  can you give an example (codish) of
how that "scheduler" works (outside our container of course, in multiple VMs
;-)

marc

|
|/Rickard
|
|
|
|


Reply via email to