[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
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