[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue 053 - WS-AT: Eliminate Replay message
This is identified as WS-TX issue 053. Please ensure follow-ups have a subject line starting "Issue 053 - WS-AT: Eliminate Replay message". -----Original Message----- From: Alastair Green [mailto:alastair.green@choreology.com] Sent: Wednesday, April 05, 2006 5:09 PM To: ws-tx@lists.oasis-open.org Subject: [ws-tx] New Issue: WS-AT: Eliminate Replay message Issue name -- WS-AT: Eliminate Replay message PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER. The issues coordinators will notify the list when that has occurred. Target document and draft: Protocol: WS-AT Artifact: spec Draft: WS-AT CD 0.1 uploaded Link to the document referenced: http://www.oasis-open.org/apps/org/workgroup/ws-tx/download.php/17325/ws tx-wsat-1.1-spec-cd-01.pdf Section and PDF line number: Section 3.4, "Two-Phase Commit Protocol", ll. 221-223 Coordinator View State Table, after l. 503 Issue type: Design Related issues: New issue: WS-AT: Replay message generates protocol errors New issue: WS-AT: Comms Times Out internal event should be removed from state tables Issue Description: Replay is a pointless message. Replay the last message sent, if any. Issue Details: Replay is a universal synonym for "resend the last message sent, if any". Better and simpler to remove it, and rest on the rule that a coordinator and a participant can both, if feeling lonely, resend the last message sent, if any. (This rule is stated in the proposed resolution to related issue: "WS-AT: Comms Times Out internal event should be removed from state tables", and is needed in any event.) Proposed Resolution: a) Remove lines 221-223. b) Remove the row labelled (Inbound Messages) Replay in the Coordinator View state table.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]