[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-msg] Reliable Messaging question
Why would an MSH continue sending retries after receiving an ErrorList
for that MessageId? Section 6.5.7 indicates that when a message cannot be
delivered then a DFN must be returned. You are right though, it doesn't
actually say not to send any more retries.
I'm a little confused... If an Acknowledgment is present with an
ErrorList, does that mean the MSH does or doesn't send a DFN to the
application? I suppose if the message got far enough so that the receiving
MSH could actually generate an Acknowledgment then that would constitute
delivery for the purposes of RM? I think this would be OK -- send an
ErrorList and an Acknowledgment together.
I'm still not clear why the sending MSH would continue to send retries if
it got an ErrorList (containing the appropriate RefToMessageId) from the
receiving MSH but without an Acknowledgment?
Regards,
David Fischer
Drummond Group.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC