[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - ex-10 - acknowledgements for LRT
This issue has been added to the btpex issue list. The issues list is posted as a Technical Committee document to the OASIS BTP TC pages on a regular basis. The current edition, as a TC document, is the most recent document with the title in the "Issues" folder of the BTP TC document list - the next posting will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.
Any protocol message that will (in theory, subject to implementation level administrative or deployment overrides) be resent indefinitely until a state-moving message is received “in reply”, should be capable of receiving a receipt-acknowledgement, whose reception can be interpreted to mean: I would prefer you not to resend the message I have just received. I will reply in my own good time, and I estimate that this time will be no less than X seconds away.
Absent such acks, it is very difficult to obtain the appropriate balance between fault-tolerance and good network citizenship. Customers don’t like excess network traffic.
The recoverable nature of all retriable conversations ensures that the use of a receipt-ack will not terminate the conversation prematurely or wrong-headedly.
The SUPERIOR_STATUS/prepared-received message might be used as a model or basis for the syntax of such a message.
Changes: 23 Mar 2004 - new issue
To comment on this issue, please follow-up to this announcement on the business-transaction@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - ex-10 - [anything]" or is a reply to such a message.
To add a new issue, please email to the issues list maintainer (Peter Furniss).
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]