[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: interposition requirements
As I said in one of the emails, if the application
wants to allow this then there's nothing we should do to prevent
it.
Agreed, but I think that this scenario is not the
majority use-case. Even in trusted intranets I know of, there are various
levels of trust, and registering all participants with the root coordinator
won't be allowed.
Having interposition cannot currupt data integrity. It
introduces another failure point, but typically the interposed coordinator is a
(or hosts a) full participant in the termination protocol anyway, so its failure
will affect the outcome one way or another.
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