Issue 4201: OTS-RTF issue: Synchronization very (too) expensive (ots-rtf)
Source: ZeroC (Mr. Bernard Normier, bernard(at)zeroc.com)
Nature: Uncategorized Issue
Severity: 
Summary: The Synchronization mechanism defined by the Transaction Service
is expensive (in terms of performance). It adds three ORB-
mediated (typically remote) calls per transaction:
- the registration call
- the before_completion call
- the after_completion call

This is far from optimal for applications that register the same
same Synchronization for all their transactions (would be nice
if a single registration could be sufficient), for applications
that don't need the before_completion callback (why pay for this
extra no-op call?), and for applications that don't need the
after_completion callback (why pay for this extra no-op call?).

Resolution: 
Revised Text: 
Actions taken:
February 15, 2001: received issue
Discussion: 

End of Annotations:=====
From: "Bernard Normier" <bernard.normier@iona.com>
To: <issues@omg.org>
Cc: <ots-rtf@omg.org>
Subject: OTS-RTF issue: Synchronization very (too) expensive
Date: Thu, 15 Feb 2001 21:04:37 -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;Pd9heXd9:E"!!b?Ne9

The Synchronization mechanism defined by the Transaction Service
is expensive (in terms of performance). It adds three ORB-
mediated (typically remote) calls per transaction:
- the registration call
- the before_completion call
- the after_completion call

This is far from optimal for applications that register the same
same Synchronization for all their transactions (would be nice
if a single registration could be sufficient), for applications
that don't need the before_completion callback (why pay for this
extra no-op call?), and for applications that don't need the
after_completion callback (why pay for this extra no-op call?).

Regards,

Bernard