[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrm] reliability of response messages
I would like to note that per rfc 2119, SHALL and MUST are one and the same. -Anish -- Durand, Jacques R. wrote: > This is a rough draft… > > Maybe this is better: > > > > *Quality of Service definition*: > > > > When the GuaranteedDelivery Agreement Item is enabled for the response > message in a request-response MEP, the following conditions must also be > satisfied: > > - GuaranteedDelivery and DuplicateElimination are also enabled > for the request message. > > Either one of the following outcomes must occur: > > (1) the Response-receiving RMP successfully delivers the response > message to its associated Consumer or > > (2) the Response-receiving RMP notifies its associated Consumer of an > exchange failure (meaning either the request or the response message > failed to be delivered). In this case, an additional delivery failure to > the Response-producer party by the Response-sending RMP may occur. > > > > (the option mentioned in the last sentence depends whether or not a > reliability ack is requested for the response message.) > > > > -J > > ------------------------------------------------------------------------ > > *From:* Abbie Barbir [mailto:abbieb@nortel.com] > *Sent:* Tuesday, May 16, 2006 3:51 PM > *To:* Durand, Jacques R.; wsrm@lists.oasis-open.org > *Subject:* RE: [wsrm] reliability of response messages > > > > Jacque, > > Something does not add up with the choice of SHALL below. If your are > saying Guranteed Delivery then SHALL SHOULD be MUST. > > > > Abbie > > > > ------------------------------------------------------------------------ > > *From:* Durand, Jacques R. [mailto:JDurand@us.fujitsu.com] > *Sent:* Tuesday, May 16, 2006 5:32 PM > *To:* wsrm@lists.oasis-open.org > *Subject:* [wsrm] reliability of response messages > > Investigating the update needed for reliability response messages > (guarateed delivery), for users who need it: > > * * > > *Quality of Service definition*: > > > > When the GuaranteedDelivery Agreement Item is enabled for the response > message in a request-response MEP, the following conditions must also be > satisfied: > > - GuaranteedDelivery and DuplicateElimination are also enabled > for the request message. > > One of the two following outcomes SHALL occur for each SubmitResponse > invocation that follows a successfully delivered SOAP request message: > either: > > (1) the Response-receiving RMP successfully delivers (DeliverResponse > invocation) the payload to its associated Consumer or > > (2) it notifies (Notify invocation) the Response-consumer of a delivery > failure for the response. > > In case (2) an additional delivery failure to the Response-producer by > the Response-sending RMP may occur. > > > > > > *Functional and Protocol Aspects*: > > > > After receiving a request message, and if a response message has been > previously sent over the back-channel for this request, then the same > response message MUST be sent again on the back-channel of any request > duplicate that is received. This assumes that the initial response is > cached (until expiration or until it is acknowledged, whichever comes > first.) > > The request message submitted with Submit operation, must use the > wsrm:Response RM-Reply Pattern. When under GuaranteedDelivery, the > response message resulting from SubmitResponse invocation, may or may > not contain a wsrm:Request element. If the Response message includes a > wsrm:Request element, this element must use Callback RM-Reply Pattern > with AckRequested element. > > > > Jacques > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]