W3C home > Mailing lists > Public > www-ws-arch@w3.org > October 2003

RE: Message reliability

From: He, Hao <Hao.He@thomson.com.au>
Date: Fri, 24 Oct 2003 08:14:00 +1000
Message-ID: <686B9E7C8AA57A45AE8DDCC5A81596AB0922DCD5@sydthqems01.int.tisa.com.au>
To: "'www-ws-arch@w3.org '" <www-ws-arch@w3.org>
Cc: "'Champion, Mike'" <Mike.Champion@SoftwareAG-USA.com>
It was agreed to accept Roger's definition in today's discussion, so the
text has been modified to reflect the decision. 

Editors of the architecture document, please incorporate the text into the

Hao Message reliability Definition
Message reliability is the degree of certainty that a message will be
and that sender and recipient will both have the same understanding of
the delivery status.

... skip ... Explanation

The goal of message reliability is to both reduce the error frequency for
messaging and to provide sufficient information about the status of a
message delivery. Such information enables a participating agent to make
a compensating decision when errors or less than desired results occur.
High level correlation such "two-phase commit" is needed if more than two
agents are involved. Note that in a distributed system, it is theoretically
not possible to guarantee correct notification of delivery; however, in
practice, simple techniques can greatly increase the overall confidence
in the message delivery.

It is important to note that a guarantee of the delivery of
messages alone does not improve the overall reliability of a Web service due
to the "end-to-end argument."[1]  It may, however, improve the performance
messaging, and therefore, the overall performance of a Web service.

Message reliability may be realized with a combination of message receipt
acknowledgement and correlation. In the event that a message has not been 
properly received and acted upon, the sender may attempt a resend, or some
other compensating action at the application level.


Received on Thursday, 23 October 2003 18:18:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:09 UTC