[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ebxml-msg] Section 3.1.6.4 TimeToLiveElement
Date: Wed, 12 Dec 2001 08:39:29 -0600 From: David Fischer <david@drummondgroup.com> +1 Except a receiving MSH does not just ignore a message passed TTL, it sends back an error -- TimeToLiveExpired. As I think I've said before, it's not clear to me that there's much value in sending back an error message in this case. What's the From MSH going to do when it gets such an error message? I guess it could use it to record metering statistics that somebody might look at. (Note that the From MSH cannot assume, from receiving such an error message, that the original message did not get through. Maybe the original message got through very quickly just fine, but also a duplicate was generated, and the duplicate arrived much later.) I'm not sure the cost of the error message is worth the benefit. But presumably this won't happen often, so the performance cost is low, so it's harmless.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC