Re: TIP - node rules

[Tom Freund <[e-mail]>]

Peter,


> There might also need to be something about the relation between the
> and the particulars would be in the TIP + application protocol P spec
> (which I agree will be bilateral in the first instances), but there are
> some rules that it might be useful to state for guidance.

> One kind of rule, essential because of the two-pipe mechanism, is making
> sure the top-node (the travel agent in the requirements example) does not
> initiate commitment until all the subordinates have registered.
> Generalising this precisely may not be that easy. A particular might be:

      Doesn't the general rule need to also state that all applications
messages must have been
received by a server ... this would be the equivalent of the
OTS/implicit/checked behavior?

     Another case, not specifically on this point but related is
out-of-sequence messages ... i.e. a failure
in the server causes the server to restart at some random point in the
application message flow (btw a
point which is not covered in the OMG/OTS specification).

Tom Freund