Issue 1317:  Name clashes with current in PropagationContext (01) (transactions)
Source:  (, )
Nature:  Clarification
Severity: 
Summary: Summary: I noticed that the latest draft of the OTS clears up the name clashes
 with Coordinator and Terminator in TransIdentity, but hasn"t fixed the
 clash with current in PropagationContext. At present I"m having to
 rename this to currentTransaction, but this may not be "official".
 
 There are a few other places in the current spec. which I think may need
 slight modifications (assuming I haven"t missed the text that covers
 them):
 
 i) the description of Current doesn"t specify what default timeout value
 will be given to begin if set_timeout has not been called prior to begin
 for the particular client thread. This may be deliberate so as to allow
 an implementation dependant choice, or it may simply be assumed to be
 zero (no timeout). Either way, I think something should be mentioned in
 the spec.
 

Resolution: 
Revised Text: 
Actions taken:
May 12, 1998: received issue
Discussion: 

End of Annotations:=====
Return-Path: <M.C.Little@ncl.ac.uk>
Date: Tue, 12 May 1998 15:00:19 +0100
From: Mark Little <M.C.Little@ncl.ac.uk>
To: juergen@omg.org
Subject: [Fwd: some more OTS clarifications]

Juergen, I sent this attached message to the OTS mailing list in March
but although it appeared it never got a reply (such as an Issue
number).
The issues raised are importent, especially those about name clashes
in
the current OTS module. Could you forward this to the relevant person,
or who should I contact? (In the past, a post to the OTS list has
usually lead to an Issue statement.)

Thanks in advance,

Mark.

-----------------------------------------------------------------------------

SENDER : Dr. Mark Little, Arjuna Project, Distributed Systems
Research.
PHONE : +44 191 222 8066, FAX : +44 191 222 8232
POST : Department of Computing Science, University of Newcastle
   upon Tyne, UK, NE1 7RU
EMAIL : M.C.Little@newcastle.ac.uk

Received: from cheviot.ncl.ac.uk (cheviot.ncl.ac.uk [128.240.233.51])
by kellah.ncl.ac.uk (8.6.12/8.6.x-cf revision 3 for Solaris 2.x) with
ESMTP id OAA14089; Mon, 23 Mar 1998 14:28:16 GMT
Received: from emerald by cheviot.ncl.ac.uk id
<OAA13029@cheviot.ncl.ac.uk>
  (8.7.6/ for ncl.ac.uk) with SMTP; Mon, 23 Mar 1998 14:30:55 GMT
Received: from cheviot.ncl.ac.uk by emerald (SMI-8.6/SMI-SVR4)
	id JAA28505; Mon, 23 Mar 1998 09:14:08 -0500
Received: from ncl.ac.uk by cheviot.ncl.ac.uk id
<OAA04203@cheviot.ncl.ac.uk>
  (8.7.6/ for ncl.ac.uk) with ESMTP; Mon, 23 Mar 1998 14:08:06 GMT
Sender: nmcl@ncl.ac.uk
Message-ID: <35166CC1.22236AC0@ncl.ac.uk>
Date: Mon, 23 Mar 1998 14:08:01 +0000
From: Mark Little <M.C.Little@ncl.ac.uk>
Organization: Arjuna Project
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i686)
MIME-Version: 1.0
To: OTS mailing list <transactions-wg@omg.org>
Subject: some more clarifications
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii

I noticed that the latest draft of the OTS clears up the name clashes
with Coordinator and Terminator in TransIdentity, but hasn't fixed the
clash with current in PropagationContext. At present I'm having to
rename this to currentTransaction, but this may not be "official".

There are a few other places in the current spec. which I think may
need
slight modifications (assuming I haven't missed the text that covers
them):

i) the description of Current doesn't specify what default timeout
value
will be given to begin if set_timeout has not been called prior to
begin
for the particular client thread. This may be deliberate so as to
allow
an implementation dependant choice, or it may simply be assumed to be
zero (no timeout). Either way, I think something should be mentioned
in
the spec.