MHonArc v2.5.2 -->
ebxml-msg message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [ebxml-msg] reliable messaging
Engkee,
You are proposing an ACK to an ACK ("UNTIL the ack has been successfully
sent to Party A and confirmed accordingly..."). Some kind of ACK to an ACK
seems to be needed as part of any solution. Anything involving an ACK to an
ACK would require added function in the MSG specification. I don't see a
way around doing that.
Solutions based on status request protocols might allow most system
failure/recovery cases to be recovered without having to start from the
beginning.
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
"Engkee Kwang"
<ekwang@vitria.co To: Martin W Sachs/Watson/IBM@IBMUS
m> cc: <ebxml-msg@lists.oasis-open.org>
Subject: RE: [ebxml-msg] reliable messaging
10/15/2002 11:54
AM
Marty,
i'm sure that i'm out of sync and missing some detail here but it would
seem that at least this problem can be avoid IF
- Party B's MSH persist the message BUT DO NOT pass it to the application
UNTIL the ack has been successfully sent to Party A and confirmed
accordingly...
- then when Party B's MSH comes back up, it should try to send the ack
AFTER checking that the time allowed has not expired. Since in this case,
the time has expired, it should consider the message to be invalid and not
pass it to the application
Engkee
>