- From: Christopher B Ferris <chrisfer@us.ibm.com>
- Date: Thu, 29 Aug 2002 17:10:45 -0400
- To: Mike Dierken <mike@dataconcert.com>
- Cc: www-ws-arch@w3.org
Received on Thursday, 29 August 2002 17:11:26 UTC
That is often an option, but not always. You can also build in mechanisms that provide for the receiver to determine if a given message is a duplicate (messageId) resulting from a resend. The receiver can choose whether to process or ignore it based on whether it can or cannot be safely processed. Cheers, Christopher Ferris Architect, Emerging e-business Industry Architecture email: chrisfer@us.ibm.com phone: +1 508 234 3624 www-ws-arch-request@w3.org wrote on 08/29/2002 05:01:31 PM: > > > > The whole point is to minimize the probability that the sender will remain > in such a state. > > And possibly to design in the capability for safely repeatable messages? >
Received on Thursday, 29 August 2002 17:11:26 UTC