Issue 4085: OTS-RTF: PropagationContext and is_same_transaction (ots-rtf)
Source: ZeroC (Mr. Bernard Normier, bernard(at)zeroc.com)
Nature: Clarification
Severity: 
Summary: otid is described as follows on p. 10-75 of ptc/00-10-03:

"otid
An identifier specific to the current transaction or subtransaction.
This value is intended to support efficient (local) execution of the
is_same_transaction and hash_transaction operations when the
importing Transaction Service does interposition".

However, it is never defined how the otid can be used to determine
when two transactions are the same:
- is comparing the "current" otids sufficient?
- or, when nested transactions are used, the otid, the parent's otid (etc.)
  need to be compared?
Resolution: 
Revised Text: 
Actions taken:
November 30, 2000: received issue
Discussion: 

End of Annotations:=====
rom: "Bernard Normier" <bernard.normier@iona.com>
To: <issues@omg.org>
Subject: OTS-RTF: PropagationContext and is_same_transaction
Date: Wed, 29 Nov 2000 17:03:32 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Type: text
X-UIDL: N`9!!~ei!!?,Yd9,3>e9

Nature: Clarification

otid is described as follows on p. 10-75 of ptc/00-10-03:

"otid
An identifier specific to the current transaction or subtransaction.
This value is intended to support efficient (local) execution of the
is_same_transaction and hash_transaction operations when the
importing Transaction Service does interposition".

However, it is never defined how the otid can be used to determine
when two transactions are the same:
- is comparing the "current" otids sufficient?
- or, when nested transactions are used, the otid, the parent's otid
(etc.)
  need to be compared?

Regards,

Bernard