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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

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


Subject: RE: T2 Retry with Delivery Receipt



I agree that even the phone call is either inconclusive or impractical in
some cases.  Customer service at my wife's health insuror has no idea
whether a claim has arrived until processing is completed.  They don't
enter it into the computer until then.

One could conclude that reliable messaging is impossible or at best it only
pushes retries down from the application to the middleware. A better
approach is to design for the .999 of the cases where it does what it is
supposed to do and then add some caveat about pathological cases.  Delivery
Failure Notification, when it is a message from the From MSG to the From
software will mean what it says except in odd cases out on the wings of the
distribution.  Having Reliable Messaging work MOST of the time is better
than not having it.

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



"David Fischer" <david@drummondgroup.com> on 09/13/2001 11:59:00 AM

To:   "Dan Weinreb" <dlw@exceloncorp.com>, Martin W Sachs/Watson/IBM@IBMUS
cc:   <ebxml-msg@lists.oasis-open.org>
Subject:  RE: T2 Retry with Delivery Receipt



Even a phone call does not guarantee lack of delivery -- it may come later
or
the administrator could miss it.  Failure can never be proven.  OTOH, if
the
administrator (or MessageStatus or end-to-end Ack) perceives a success,
this
should be definitive.  Even for success, an end-to-end Retry may be
necessary to
get a required NRR (DR).

Confirmation of non-delivery is not really possible (Logic 101 -- you can
never
prove a negative).  TTL may come into play here and help resolve this but
TTL is
likely to be too long for time-sensitive issues.

Regards,

David Fischer
Drummond Group.

-----Original Message-----
From: Dan Weinreb [mailto:dlw@exceloncorp.com]
Sent: Thursday, September 13, 2001 10:32 AM
To: mwsachs@us.ibm.com
Cc: david@drummondgroup.com; ebxml-msg@lists.oasis-open.org
Subject: Re: T2 Retry with Delivery Receipt


   Date: Thu, 13 Sep 2001 09:03:02 -0400
   From: Martin W Sachs <mwsachs@us.ibm.com>

              So the phone call might be necessary to confirm that the
   message was not received.

Or you can try MessageStatus over and over until, at last, you get an
answer.






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


Powered by eList eXpress LLC