Re: T2, Proposed solution for ... Re: SyncReply andReliableMessagingMethod in QualityOfServiceInfo

[Martin W Sachs <mwsachs@us.ibm.com>]

Duplicate detection is essential if retries are permitted.  A retry may
result in a duplicate message if the To party received it but the From
party did not receive the ACK.

By the say, here is one possible way to protect against the To party
receiving the message but the From party never receives any ACKs.  Perhaps
once could define that if the To party receives N copies of the same
message, where N is the number of permitted retries, that something is
badly wrong and the To MSH should not deliver the message.

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
*************************************************************************************



Dan Weinreb <dlw@exceloncorp.com> on 08/17/2001 08:45:46 AM

Please respond to Dan Weinreb <dlw@exceloncorp.com>

To:   david@drummondgroup.com
cc:   ebxml-msg@lists.oasis-open.org
Subject:  Re: T2, Proposed solution for ... Re: SyncReply and
      ReliableMessagingMethod in QualityOfServiceInfo



   Date: Thu, 16 Aug 2001 21:36:10 -0500
   From: David Fischer <david@drummondgroup.com>

   RM does not automatically imply duplicate detection.

I'm not sure I understand what you're implying by this.  Are you
saying that if a From Party sends a single message, and a To Party
reacts by presenting two copies of that message to the To Application,
as if two separate messages had been sent, then you'd still want to
call that "reliable messaging"?

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>