[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [bt-spec] BTP Issue 53 : will or may contradict ?
We should
not be assuming anything about the environment in which BTP will "typically" be
used. As a result, it's not an objective statement to say it's a "very special
case", since that in itself is based on certain assumptions about deployment. I
don't mind "usually", but what I do want is some text along the lines
of:
"If the
coordinator is issuing the second phase of a successful (i.e., CONFIRM)
completion protocol synchronously, then it is possible upon the receipt of a
CANCEL message from the first non-RESIGNED participant for the
coordinator to change it's decision to CANCEL the atom, and in such a way
prevent a CONTRADICTION from occurring. Otherwise ..."
I would like
to avoid contradictions as much as possible, because cleaning up after them is
going to be a nightmare for system administrators, especially if they are spread
across the planet. It's exactly the same argument as for this kind of
optimisation in TPs with heuristics.
Mark.
----------------------------------------------
Dr. Mark Little Transactions Architect, HP Arjuna Labs Email: mark@arjuna.com | mark_little@hp.com 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