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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm message

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


Subject: RE: [wsrm] Rel-113 (Message delivery/processing after fault)


Sunil:
Case 1- a message requires an Ack, yet the receiver does not implement this feature.
Should the Receiver drop the message and just send back the Fault? Why not deliver
the message?
 
 It all should  depend on the mustUnderstand (mU) attribute. If the mU=1, and the
 receiver doesn't understand it, then it MUST generate a Fault and message should
 not be delivered.
[Jacques Durand] I realize that we always generate a SOAP fault for every RM fault header element (should we make that more explicit in spec). If that is teh case then yes, although the decision how to interpret "understand" being the RMP decision, the level of processing done to the message before deciding of a fault could include delivery to upper layer if we wanted.
In any case, I agree now we should not "RMP-deliver" on a fault...

 If mU=0, then if the receiver understands it, then it will deliver and send an Ack. back
 and if if the receiver doesn't understand it, it MUST still deliver the message.
[Jacques Durand] I believe we always require mU=1 for RM headers, so that case should not occur? If "does not understand" means an RM failure, we would not deliver I guess - I think you talk about the SOAP node "delivery" , not RMP delivery.
 
 
  
Jacques 


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