RE: [bt-spec] BTP Issue 105 : Qualifier to allow automatic completionof all-cancelled cohesions

[Tony Fletcher <tony_fletcher@btopenworld.com>]

Dear Colleagues,

 

I am not convinced that this is a worthwhile change and therefore would propose a solution of 'No Change'.

 

Firstly I do think a qualifier should be used for something that changes the state and allowed sequence of messages - and the proposed change clearly does.  So if we were to adopt this change then it should be a proper parameter not a qualifier.

 

But frankly this kind of delegation does not seem very wise to me (i.e. is it really good defensive programming practice?).   An application could easily find that a cohesion it thought was still live has been blown away or conversely that one that it thought the decider would blow away because all inferiors had cancelled is actually still live because an inferior remains.  Thus it seems much safer to me to use an explicit CANCEL_TRANSACTION. 

 

Best Regards     Tony

A M Fletcher

Choreology Ltd., 13 Austin Friars, London EC2N 2JX     UK

Tel: +44 (0) 20 76701787         Mobile: +44 (0) 7801 948219

tony.fletcher@choreology.com     (Home: amfletcher@iee.org)

-----Original Message-----
From: BTP issues maintainer [mailto:peter.furniss@choreology.com]
Sent: 22 February 2002 14:55
To: bt-spec@lists.oasis-open.org
Subject: [bt-spec] BTP Issue 105 : Qualifier to allow automatic completion of all-cancelled cohesions

This issue has been added to the BTP issue list

BTP Issue 105 : Qualifier to allow automatic completion of all-cancelled cohesions

Submitter: Mark Little, HP
Category: minor 
technical
Description:
In a traditional transaction system (and 
presumably for atoms), if I issue a prepare and get back cancel/readonly from 
all participants, I don't have to send anything else to that transaction because 
I know it has finished. With cohesions, the situation is different. In some 
cases I'd like implementations to be able to free up resources held by the 
coordinator implementation immediately simply because there won't be any other 
registrations and the application shouldn't have to explicitly terminate 
such a cohesion which now has no members. 
Suggested solution:
Have 
a standard qualifier such that, if following PREPARE_INFERIORS and/or 
CANCEL_INFERIORS all the current inferiors have either cancelled or resigned 
gone away, then the cohesion is finished, and replies with 
TRANSACTION_CANCELLED. Default is not (CANCEL_TRANSACTION would be required).

---

To comment on this issue, please follow-up to this announcement on the bt-spec@lists.oasis-open.org (replying to this message should automatically send your message to that list).

The current draft, with line numbers is available in pdf format and word format.

To add a new issue, please email to Peter Furniss peter.furniss@choreology.com. It helps if you propose a category (technical, minor technical, editorial, minor editorial).