[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: interposition requirements
At 10:54 AM 5/1/01 +0100, Mark Little wrote: ><<<< >We can neither disallow (sub participants registering with coordinator) >nor force. There is no way that coordinator can know it... and looks like >hiding the subtransaction will not harm the transaction anyway.. so the >coordinator site may want to include its wish to have a flat transaction >structure(all the participants register with the coordinator) and >participants may try to comply with it (if they wish!) > >>>> >Subtransaction? Sub-coordination surely? Interposition isn't the same as >subtransaction (or nested transaction). > I do not mean a sub-transaction or netsted transaction per proper definition.. Ok, lets call it a new transaction, a transaction that the main coordinator is not aware of, but its outcome may affect the transaction that the main coordinator is managing. >Mark. > >---------------------------------------------- >Dr. Mark Little (<mailto:mark@arjuna.com>mark@arjuna.com) >Transactions Architect, HP Arjuna Labs >Phone +44 191 2064538 >Fax +44 191 2064203 > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC