state table event explanation

[Peter Furniss <peter.furniss@choreology.com>]

This is the key to the state table, since it tries to define what the
application and recovery implications are of the confirm sequence etc. by
saying what the "decision events" mean.

Not complete, since I haven't worked through the Cohesion aspects, though I
think they may be easier than I first thought. But clear enough to see how
it goes I think.

Critical thing is to keep the phrasing open enough so the full range of
potential BTP-using applications (including e.g. long-running; short-term;
compensation-based; xa-style; volatile resource; participant timers out;
buy/sell confirms) can use BTP, gaining the consistency promises of BTP but
without contradicting the specifications requirements.

As Alastair said, we have some (I hope minor) terminology alignment to sort
out between his and my pieces.

Peter

------------------------------------------
Peter Furniss
Technical Director, Choreology Ltd
email:  peter.furniss@choreology.com
phone:  +44 20 7670 1679
direct: +44 20 7670 1783
mobile: 07951 536168
13 Austin Friars, London EC2N 2JX

2001-07-23.OASIS.BTP.State table events.doc