[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-tx] Groups - WS-TX Bi-Weekly Concall modified
Ian, Eric, I'm afraid I won't be able to be on most of the call tomorrow - I hope to make the first 20-25 minutes. The good news (well, I hope you think it's good) is that I will be able to come to the Dublin face-to-face. I must also confess I have not yet done either of the AI's against me - the fault handling rule pointer I was going to wait until the text was integrated (it's a very minor editorial anyway, I think I'm prepared to rely on editorial pride in producing an intelligible document to determine if it is needed :-). On the names for the three uses of Coordinator for issue 035, I mostly haven't had time. Since the text changes are editorial (though the distinction in concepts will, I think, clarify discussion in general), it perhaps can follow the issues that affect implemenation and interoperation. If I may make so bold as propose resolutions to some of the other issues on the agenda, in case they get discussed when I'm not on the call. Several of these have been chased round the email list already. I'd suggest 043 is dealt with before 039, as 043 concerns may contaminate 039 discussion if they are done in numerical order. i043 - WS-AT: Invalid state inappropriate response to orphaned volatile participants At least for volatile (see 039) the response should be a new terminating message/fault "UnknownTransaction", with the other changes as in the proposal for this issue as submitted (I now think UnknownTransaction is a better name than UnknownTransactionOutcome) i039 - WS-AT: Coordinator should not distinguish protocol of orphaned participants Unknown Transaction should be the response for durables too. See email discussion i052 - WS-AT: Replay message generates protocol errors (I think this is misnamed - I think "... causes unnecessary aborts" might be more helpful) have we seen any justification as to why replay/preparing must be considered sufficent cause for an abort of a transaction. I challenge the submitters to provide reasons that are compelling and valid for the send-on-outbound-connection pattern of ws-at. :-) [and remember the state table says all MUST abort in this case; changing would still allow an implementation to abort if it chose or was built to do so] i053 - WS-AT: Eliminate Replay message this depends on 052 - it is impossible to discuss until 052 is resolved, because the possible additional semantics of replay / recovery are overwhelmed by the current actual semantics of the abort if received in Preparing. i055 - WS-AT: User Commit and User Rollback should not return Aborted in None state they should return UnknownTransaction (when they are synonyms for Commit, Rollback in Completion protocol), or equivalent semantic (when not.) i056 - WS-AT: User Commit and User Rollback row of CV state table contradicts resolution of 010 as 055 Hope you don't mind me emailing what I would have like to have said in realtime. See you in Dublin Peter -----Original Message----- From: ian_robinson@uk.ibm.com [mailto:ian_robinson@uk.ibm.com] Sent: 17 May 2006 17:14 To: ws-tx@lists.oasis-open.org Subject: [ws-tx] Groups - WS-TX Bi-Weekly Concall modified Updated list of Action Items -- Dr Ian Robinson WS-TX Bi-Weekly Concall has been modified by Dr Ian Robinson Date: Thursday, 18 May 2006 Time: 11:30am - 01:00pm ET Event Description: US (toll free) 866-505-4412 UK (toll free) 0800 279 9193 Int'l (toll) +44-20-7019-0808 Passcode: 268450 Chat room: http://webconf.soaphub.org/conf/room/wstx Agenda: 1. Roll Call - chair 2. Confirm Paul Knight as minute taker - chair 3. Approve minutes of May 4 telecon - chair 4. Call for AOB - chair 5. Action Review - Paul K Max: Draft text for security composability for WS-AT. Bob Freund: submit issue against banning Anonymous replyTo in CreateCoordinationContext. Tom: submit issue on removing the designation of notifications as faults. Ian: cover how the test plans will react to the resolution to issue 30. Peter: consider submitting issue on pointing to fault handling rules in WS-AT. Peter: restate proposed text addressing Issue 35. Editors of specs and interop docs: get drafts ready a week before the F2F. 6. Potential new issues to accept - Ram Brief statement of each proposed new issue. There is no need to consider the merit of any proposed resolution at this stage. In general the TC will accept issues that are not reopening resolved issues and that are in-scope. Accepted issues move from "review" state to "active" state. 7. Agenda and logistics for Dublin F2F - Eric. 8. Issue resolution i035 - ws-tx: term "coordinator" overloaded i045 - WS-AT: Meaning of "wsp:Optional i039 - WS-AT: Coordinator should not distinguish protocol of orphaned participants i043 - WS-AT: Invalid state inappropriate response to orphaned volatile participants i052 - WS-AT: Replay message generates protocol errors i053 - WS-AT: Eliminate Replay message i055 - WS-AT: User Commit and User Rollback should not return Aborted in None state i056 - WS-AT: User Commit and User Rollback row of CV state table contradicts resolution of 010 9. AOB 10. Straggler Roll Call 11. Close Minutes: This event is one in a list of recurring events. Other event dates in this series: Thursday, 01 December 2005, 11:30am to 01:00pm ET Thursday, 15 December 2005, 11:30am to 01:00pm ET Thursday, 12 January 2006, 11:30am to 01:00pm ET Thursday, 26 January 2006, 11:30am to 01:00pm ET Thursday, 09 February 2006, 11:30am to 01:00pm ET Thursday, 23 February 2006, 11:30am to 01:00pm ET Thursday, 09 March 2006, 11:30am to 01:00pm ET Thursday, 23 March 2006, 11:30am to 01:00pm ET Thursday, 06 April 2006, 11:30am to 01:00pm ET Thursday, 20 April 2006, 11:30am to 01:00pm ET Thursday, 04 May 2006, 11:30am to 01:00pm ET Thursday, 01 June 2006, 11:30am to 01:00pm ET Thursday, 15 June 2006, 11:30am to 01:00pm ET Thursday, 29 June 2006, 11:30am to 01:00pm ET Thursday, 13 July 2006, 11:30am to 01:00pm ET Thursday, 27 July 2006, 11:30am to 01:00pm ET Thursday, 10 August 2006, 11:30am to 01:00pm ET Thursday, 24 August 2006, 11:30am to 01:00pm ET Thursday, 07 September 2006, 11:30am to 01:00pm ET Thursday, 21 September 2006, 11:30am to 01:00pm ET Thursday, 05 October 2006, 11:30am to 01:00pm ET Thursday, 19 October 2006, 11:30am to 01:00pm ET Thursday, 02 November 2006, 11:30am to 01:00pm ET Thursday, 16 November 2006, 11:30am to 01:00pm ET Thursday, 30 November 2006, 11:30am to 01:00pm ET View event details: http://www.oasis-open.org/apps/org/workgroup/ws-tx/event.php?event_id=89 90 PLEASE NOTE: If the above link does not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]