[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ws-tx] Issue 079 - WS-AT: state tables - "Forgetting" state
I believe the resolution I proposed to issue 81 also addresses this issue. Specifically: 1. Delete the All Forgotten row from the CV state table. 2. All CV cells with an Action of "Forget" should be changed to show a state transition to "None". So, for example, in the CV table [ReadOnly, Active] would be changed to: Forget None Regards, Ian "Ram Jeyaraman" <Ram.Jeyaraman@mi crosoft.com> To <ws-tx@lists.oasis-open.org> 10/07/2006 21:38 cc Subject [ws-tx] Issue 079 - WS-AT: state tables - "Forgetting" state This is identified as WS-TX issue 079. Please ensure follow-ups have a subject line starting ‘Issue 079 - WS-AT: state tables - "Forgetting" state’. From: Peter Furniss [mailto:peter.furniss@erebor.co.uk] Sent: Monday, July 10, 2006 1:08 PM To: Ram Jeyaraman Subject: new issue - WS-AT: state tables - "Forgetting" state Issue name -- WS-AT: state tables - "Forgetting" state PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER. The issues coordinator will notify the list when that has occurred. Target document and draft: Protocol: WS-AT Artifact: spec Draft: AT spec cd 2 Link to the document referenced: http://www.oasis-open.org/committees/download.php/18889/wstx-wsat-1.1-spec-cd-02.doc Section and PDF line number: section 10, coordinator view state table Issue type: Editorial Related issues: Issue 036 : WS-AT - Coordinator state machine incomplete Issue 048 : WS-AT - Internal events and actions undefined New issues: Issue Description: Readonly leaves the coordinator in Active state which will cause it to send protocol in reaction to internal events, contrary to the state diagram. Issue Details A coordinator receiving ReadOnly from a Participant should end the protocol exchanges. However, the table currently has the state staying in Active (The "Forget" action has to be understood as initiating forget, as the transitions to None are distinct) If User Commit or User Rollback are received while this state engine is still in the Active state, the table says Prepare or Rollback would be sent. ReadOnly needs to move the state to one where User Commit and User Rollback are ignored. A related problem is the two User actions are not permitted in Aborting - which is correct since we would not allow duplicate User Rollback, but incorrect if the transition to Aborting was caused by the spontaneous arrival of Aborted in Active state. Proposed resolution Add a state "Forgetting", which is entered by all cells that have Forget as an action. All incoming messages have action Ignore, except for Prepared, and User Commit, User Rollback, Initiate Rollback, Expires Times Out are all ignored. All Forgotten causes transition to None. receive Prepared/Forgetting has action (re)Send Rollback.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]