summaryrefslogtreecommitdiff
path: root/TAO/docs
diff options
context:
space:
mode:
authorbala <balanatarajan@users.noreply.github.com>2002-04-30 22:41:30 +0000
committerbala <balanatarajan@users.noreply.github.com>2002-04-30 22:41:30 +0000
commit9667203c13390dc44f7e204c29a0616fa543db63 (patch)
tree4638f6bb26e4c1ff80dcc72e1458d17aa2ebff79 /TAO/docs
parent4651aa6f7eae615431888efa4f31a8309e44509f (diff)
downloadATCD-9667203c13390dc44f7e204c29a0616fa543db63.tar.gz
ChangeLogTag: Tue Apr 30 17:39:37 2002 Balachandran Natarajan <bala@cs.wustl.edu>
Diffstat (limited to 'TAO/docs')
-rw-r--r--TAO/docs/Options.html30
1 files changed, 15 insertions, 15 deletions
diff --git a/TAO/docs/Options.html b/TAO/docs/Options.html
index 0eb840f7732..633c0f8ad41 100644
--- a/TAO/docs/Options.html
+++ b/TAO/docs/Options.html
@@ -551,14 +551,6 @@ would load all the options listed within "".
</TD>
</TR>
<TR>
- <TD><CODE>-ORBConnectionLock</CODE> <EM>locktype</EM></TD>
- <TD><a name="-ORBConnectionLock"></a>
- This option deprecated. Usage of this option will switch usage
- automatically to "-ORBConnectionCacheLock". Please see the
- documentation of "-ORBConnectionCacheLock" for details.
- </TD>
-</TR>
-<TR>
<TD><CODE>-ORBConnectionCacheLock</CODE> <EM>locktype</EM></TD>
<TD><a name="-ORBConnectionCacheLock"></a>
Specify the type of lock to be used by the Connection
@@ -868,14 +860,22 @@ would load all the options listed within "".
</TD>
</TR>
-
<TR>
- <TD><CODE>-ORBConnectorLock</CODE> <EM>lock type</EM></TD>
- <TD><a
- name="-ORBConnectorLock"></a> This option has been deprecated.
- </TD>
- </TR>
-
+ <TD><CODE>-ORBConnectStrategy</CODE> <EM>type</EM></TD>
+ <TD><a name="-ORBConnectStrategy"></a>
+ TAO provides three strategies to connect to remote servers.
+ The default <CODE>leader_follower</CODE> strategy uses the
+ Reactor and non-blocking connects to connect and this strategy
+ participates in the Leader/Followers protocol to synchronize
+ access to the Reactor. The <CODE>reactive</CODE> strategy uses
+ the Reactor for non-blocking connects but does not take part in
+ the Leader/Followers protocol, thus it is better used only in
+ single threaded applications. Finally, the <CODE>blocking</CODE>
+ strategy as the name implies, blocks the thread until
+ connection is complete. Some of the protocols in TAO viz. SHMIOP
+ and SSLIOP can only use blocked strategy.
+ </TD>
+</TR>
</TABLE>
</P>
</BLOCKQUOTE>