[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: interposition requirements
> We can always define and disallow it per definition but it looks like an > artificial restriction... because a service can always go around it by > starting its own transaction under the cover and the main coordinator > cannot do anything, cannot even aware of this new transaction. The default should be that it interposition is available from a participant then it should be used. However, I've nothing against it being a configurable option as long as it is up to the participant to decide whether it wants to allow it to be turned off. Mark. ---------------------------------------------- Dr. Mark Little (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