Issue 816:  Current set_timeout clarification (transactions)
Source:  (, )
Nature:  Clarification
Severity:  Minor
Summary: Summary: There may be a requirement to clarify description of the set_timeout method of Current.The description in the spec. isn"t too clear on this and could be read as a "global" setting of tieouts

Resolution: 
Revised Text: 
Actions taken:
November 27, 1997: received issue
Discussion: 

End of Annotations:=====
Return-Path: <M.C.Little@newcastle.ac.uk>
Date: Thu, 27 Nov 1997 10:28:40 +0000
From: Mark Little <M.C.Little@newcastle.ac.uk>
Organization: Dept. of Computing Science, Newcastle University
To: transactions@omg.org
Subject: Current set_timeout clarification

I know that Current is described as a pseudo-object which creates
and terminated transactions on a per thread basis but I think there
maybe a requirement to clarify to description of the set_timeout
method of Current.

I'm assuming, since it is supposed to work similarly to
the X/Open tx_set_transaction_timeout operation, that the timeout
values are set on a per thread basis, i.e., one call to set_timeout
will

not affect transactions created by another thread. However, after
discussions with other people it's apparent that the description in
the
spec. isn't too clear on this and could be read as a "global" setting
of timeouts.

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