ebxml-cppa message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: [ebxml-cppa] RE: Draft paper from Choreology on Transaction Managementin ebXML
- From: Tony Fletcher <tony.fletcher@choreology.com>
- To: "BCPS (list) " <ebtwg-bcs@lists.ebtwg.org>,BPSS List Ebtwg <ebtwg-bps@lists.ebtwg.org>,Ebxml-Cppa List <ebxml-cppa@lists.oasis-open.org>
- Date: Fri, 06 Sep 2002 16:26:31 +0100
Title: Message
Dear
Colleagues,
I do
humbly apologise for bombarding you all again, but like all good 'software'
there was one more bug to find! I have corrected the two figure captions
in the appendix and completed the appendix, which outline the presumed abort and
presume nothing algorithms.
Please
replace previous version with the attached copy -
thanks.
And
thanks to those who have already responded to the paper. After the Geneva
(UN/CEFACT Forum) we will be carefully considering all the
feedback.
To
clarify a couple of points made:
This
document has no formal status in UN/CEFACT at all. It is a contribution to
the ongoing work on ebXML within UN/CEFACT (and OASIS
too).
People
may need to distinguish between ACID - which stands for Atomicity, Consistency,
Isolation and Durability. Note that the paper only considers the
first of these four - atomicity.
Protocols can achieve atomicity (or not).
Consistency and durability are more of a wish - and definitely system
concerns. Isolation is more interesting. It is mostly a system
concern, but can have an interaction with the protocol. BTP allows parties
to decide how the will handle isolation issues. The UMM does not appear to
consider isolation issues explicitly - and I think it should (issues of a party
/ system processing concurrent business transactions which have overlaps on the
resources they concern).
Best Regards
Tony
A M Fletcher
Cohesions 1.0 (TM)
Business transaction management software for
application coordination
Choreology Ltd., 13 Austin Friars, London
EC2N 2JX UK
Tel: +44 (0) 20
76701787 Mobile: +44 (0) 7801
948219
Dear
Colleagues,
Please find attached
a draft paper on transaction management in ebXML. It compares the transaction capabilities
currently available (very simple, single action, single party and not fully
respecting of responder autonomy) with those which would be available if BTP
were to be included (relatively rich set of features - particularly
multi-action, multi-party and respectful of each parties autonomy), and also
considers a 'middle way' of extending the current approach (multi-action and
multi-party, but not fully respecting of responder
autonomy).
It is hoped that this paper will stimulate
discussion and lead to further clarification - as it says on the front of the paper -
your constructive comments and suggestions will be most
welcome.
Best
Regards,
Tony
|
Tony
Fletcher
Technical
Advisor
Choreology
Ltd. 13, Austin Friars, London EC2N 2JX UK |
Phone:
|
+44
(0) 20 7670 1787 |
Mobile:
|
+44
(0) 7801 948 219 |
Fax:
|
+44
(0) 20 7670 1785 |
Web: |
www.choreology.com |
Cohesions
1.0™ |
Business
transaction management software for application
coordination |
Home: amfletcher@iee.org |
tony.fletcher@choreology.com
Attachment:
2002-09-05_ebXML_Transaction_Management.doc
Description: MS-Word document
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC