ebxml-msg — archive

RE: T2 Clarify TimeToLive

From: System
To: [email protected]
Date: Wed, 12 Sep 2001 15:39:00 -0000

While we are at it, it is not at all clear if a message that has already been persisted should be destroyed by the MSH when TTL has expired. Once the message has been persisted (and the application notified that it is there), it is already in the application domain. Message level time-to-live functions are useful at the message layer to prevent a message from circulating endlessly without being delivered (the IP hop count is an example of this). TTL functions related to staleness of the transaction are an application matter. 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 ************************************************************************************* "Burdett, David" <[email protected]> on 09/12/2001 02:51:38 PM To: "'Dan Weinreb'" <[email protected]> cc: [email protected], [email protected], [email protected] Subject: RE: T2 Clarify TimeToLive Dan The spec already says that an error should be reported if the To MSH receives a message where Time To Live has passed. It doesn't though say that the message must be ignored. This is a small useful clarification. David