[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New Issue: WS-AT: Comms Times Out internal event should be removedfrom state tables
Issue name -- WS-AT: Comms Times Out internal event should be removed from state tables 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/wstx-wsat-1.1-spec-cd-01.pdf Section and PDF line number: Coordinator View State Table, after l. 503 Participant View State Table, after l. 510 Issue type: Design Related issues: New issue: WS-AT: Internal events and actions undefined Issue Description: Comms Times Out internal event and its concomitant action (do it again) is universally applicable to all send/resend situations. These are not (cannot feasibly) be called out as separate states. This vitiates the purpose of the event in the tables. Issue Details: None. Proposed Resolution: a) Remove the rows labelled "Comms Times Out" in both CV and PV state tables. b) Add a note (either in Section 9 or in Section 10) saying: "Note that any attempt to send a notification message may result in a communications failure. It is always legitimate to attempt a retry in such circumstances. It is also legitimate to retry a send if an expected response has not been received in a timely fashion. The definition of "timely" and the retry strategy used are implementation concerns. However, complete failure to retry in all circumstances will almost certainly lead to hung transactions."
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]