Issue 775:  checked/unchecked transaction behaviour (transactions)
Source:  (, )
Nature:  Uncategorized Issue
Severity:  Minor
Summary: Summary: Chapter 10.4.3 (page 10-32 explains the concept of checked transaction behaviour. The opposite concept, unchecked transaction behaviour does not make sense.. It may not ensure the ACID properties of a transaction. Please clarify

Resolution: 
Revised Text: 
Actions taken:
October 29, 1997: received issue
Discussion: 

End of Annotations:=====
Return-Path: <mf9@irz301.inf.tu-dresden.de>
Date: Wed, 29 Oct 1997 10:54:33 +0100
From: Mike Fischer <mf9@irz.inf.tu-dresden.de>
To: transactions@omg.org
CC: Wolfgang.Schulze@inf.tu-dresden.de,
Birgit.Demuth@inf.tu-dresden.de
Subject: checked/unchecked transaction behavior

Dear all,

In my master thesis i'm deal with the teamwork between the
CORBAservice "Persistent Object Service" and the CORBAservice
"Object Transaction Service". As a result a will elaborate
requirements at such services.

In the capter 10.4.3 (page 10-32) of the Object Transaction Service
specification is explained the concept of checked transaction
behavior.
This concept is clear, i am understand it. But the opposite concept -
unchecked transaction behavior - it doesn't mean anything to me. In my
opinion unchecked transaction behavior may not ensure the ACID
properties
of a transaction and therefore it don't make sense.

Question:
Can someone explain how unchecked transaction looks like und please
give
a
little example of the use of unchecked transaction?

Thanks.

With best regards

Mike Fischer.


****************************************************************************

|         organization:  Dresden University of Technology, Germany
|                        Department of Computer Science
|         name        :  Mike Fischer
|         e-mail      :  mf9@irz.inf.tu-dresden.de
|         www         :  http://www.inf.tu-dresden.de/~mf9
|         phone       :  +49-3501-441466
****************************************************************************