OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bt-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [bt-spec] BTP Issue 80 : CONTEXT_REPLY unnecessary forCONTEXT/cohesion


Liberty Corner discussion touched on this and seemed to accept the concept - for a  CONTEXT/cohesion, there is no
requirement to ensure that all the propagations of the CONTEXT are "counted back" with either CONTEXT_REPLY/completed or CONTEXT_REPLY/related and successful enrollment.
 
Details are in draft 0.9.0.4, in particular in the related group text for CONTEXT & application message and CONTEXT_REPLY & ENROL.
An Inferior attempting to enrol with a cohesive superior shall have the ability to ensure its enrollment by sending CONTEXT_REPLY/repudiated if its ENROL fails. If using ENROL/no-rsp-req, sent with CONTEXT_REPLY, it can achieve the same effect by setting CONTEXT_REPLY/related; CONTEXT_REPLY/completed & ENROL/no-rsp-req means the failure of the enrollment can be ignored - this is only to be allowed if the CONTEXT was atomic.
 
 
Peter

BTP Issue 80 : CONTEXT_REPLY unnecessary for CONTEXT/cohesion

Submitter: Choreology
Category: minor technical
Description:
There appears to be no requirement derived from "checking" for a CONTEXT_REPLY to be received if the CONTEXT was for a cohesion.

CONTEXT_REPLY for an Atom is to ensure that all attempted enrols for the atom worked, and avoid risk of an "orphan" inferior that the coordinator doesn't know about when it confirms. If there were such, the atom could apparently confirm when work has been done in the atom that isn't known about - the rest of the atom confirms and this orphan will (probably) eventually cancel. To prevent this, checking rules apply - until the CONTEXT_REPLY comes back, confirmation is not allowed.

But with a propagated *Cohesion* CONTEXT, there is no reason why Inferiors can't be missed out. The Terminator will determine the confirm-set on the basis of which Inferiors are enrolled - if it has an acceptable set, but there is a late-arriving ENROL, that would-be inferior just gets missed out.

There is a possibility that something that tried to ENROL in a Cohesion but failed to contact the Superior might want to send CONTEXT_REPLY/repudiated back towards the application initiator to say that there was a problem.

CONTEXT_REPLY for a cohesion may also be needed in the one-shot case (see separate issue on one-shot) 
  



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC