summaryrefslogtreecommitdiff
path: root/TAO/docs/Options.html
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/docs/Options.html')
-rw-r--r--TAO/docs/Options.html111
1 files changed, 29 insertions, 82 deletions
diff --git a/TAO/docs/Options.html b/TAO/docs/Options.html
index 9f87f4aeedb..af1936aba0d 100644
--- a/TAO/docs/Options.html
+++ b/TAO/docs/Options.html
@@ -39,7 +39,7 @@ method will consume, <EM>i.e.</EM>, remove from the vector, any
options that it recognizes.</P> </blockquote>
<HR><P>
-<H3><A NAME="ev">Environment Variables</A></H3>
+<H3>Environment Variables</H3>
The following environment variables are supported by TAO:
@@ -68,6 +68,11 @@ Specifies which IOR the Trading Service is listening on.
<TD>
Specifies which port the Trading Service is listening on.
</TD></TR>
+<TR>
+<TD><CODE>TAO_ORB_DEBUG</CODE> <EM>which</EM></TD>
+<TD>
+Enables TAO debugging mode.
+</TD></TR>
</TABLE>
</P>
</BLOCKQUOTE>
@@ -121,27 +126,24 @@ componentry.</TD></TR>
more output (try 10).
</TD></TR>
<TR>
-
-<TD><CODE>-ORBhost</CODE> <EM>hostname</EM></TD> <TD><a
-name="-ORBhost"></a>Tells the ORB to listen for requests on the
-interface associated with the host named
-<I><EM>hostname</EM></I>.</TD></TR>
-
+<TD><CODE>-ORBhost</CODE> <EM>hostname</EM></TD>
+<TD><a name="-ORBhost"></a>Tells the Object Adapter to listen for requests on the interface associated
+with the host named <I><EM>hostname</EM></I>.</TD></TR>
<TR>
-
-<TD><CODE>-ORBport</CODE> <EM>portspec</EM></TD> <TD>Tells the ORB to
-listen for requests on the port specified by
-<I><EM>portspec</EM></I>. If not specified, the OS gets to choose a
-random empty port.</TD>
-
-</TR>
-
+<TD><CODE>-ORBport</CODE> <EM>portspec</EM></TD>
+<TD>Tells the Object Adapter to listen for requests on the port specified by
+<I><EM>portspec</EM></I>, which can be a name as found in <TT>/etc/services</TT>
+or a number. The default is <TT>10013</TT>.</TD></TR>
<TR>
<TD><CODE>-ORBobjrefstyle</CODE> <EM>which</EM></TD>
<TD>Specifies the user-visible style of object references. The range of values
is <CODE>IOR</CODE>, which is the traditional nonsensical object reference,
or <CODE>URL</CODE>, which looks more like a URL.</TD></TR>
<TR>
+<TD><CODE>-ORBtablesize</CODE> <EM>object table size</EM></TD>
+<TD>Specifies the size of the object table as a positive, non-zero integer.
+If not specified, the default is <TT>64</TT>.</TD></TR>
+<TR>
<TD><CODE>-ORBrcvsock</CODE> <EM>receive buffer size</EM></TD>
<TD><A NAME="-ORBrcvsock"></a>Specify the size of the socket receive buffer as a positive, non-zero integer.
If not specified, the system-dependent default is used.</TD></TR>
@@ -214,45 +216,15 @@ copied instead of appended to the CDR stream.</TD></TR>
(<em>which</em> = <code>global</code>) or a thread-specific
(<em>which</em> = <code>tss</code>) instance for the resources it returns.</TD></TR>
<TR>
+<TD><CODE>-ORBpoa</CODE> <EM>which</EM></TD>
+<TD><a name="-ORBpoa"></a>Specify whether each thread uses a global
+(<em>which</em> = <code>global</code>) or a thread-specific
+(<em>which</em> = <code>tss</code>) instance for the Root POA.</TD></TR>
+<TR>
<TD><CODE>-ORBreactorlock</CODE> <EM>which</EM></TD>
-<TD><a name="-ORBreactorlock"></a>Specify whether the ORB reactor is
- thread-safe
+<TD><a name="-ORBcoltable"></a>Specify whether the ORB reactor is thread-safe
(<em>which</em> = <code>token</code>) or not
-(<em>which</em> = <code>null</code>). Default is <code>token</code>.
- <P>This option has been superseeded by
- <CODE>-ORBreactortype</CODE>
- </P>
-</TD></TR>
-<TR>
-<TD><CODE>-ORBreactortype</CODE> <EM>which</EM></TD>
-<TD><a name="-ORBcoltable"></a>Specify what kind of reactor does the
- ORB use, the options are:
- <TABLE BORDER="1" CELLSPACING="2" CELLPADDING="0">
- <TR><TH><em>which</em></TH><TH>Reactor</TH></TR>
- <TR><TD><CODE>select_mt<CODE></TD><TD>Use the
- <CODE>ACE_Select_Reactor</CODE> with the usual
- locking mechanism for this platform</TD></TR>
- <TR><TD><CODE>select_st<CODE></TD><TD>Use the
- <CODE>ACE_Select_Reactor</CODE> with null locks
- </TD></TR>
- <TR><TD><CODE>fl_reactor<CODE></TD><TD>Use the
- <CODE>ACE_FlReactor</CODE> only available if ACE
- was compiled with support for the FL toolkit
- </TD></TR>
- <TR><TD><CODE>xt_reactor<CODE></TD><TD>Use the
- <CODE>ACE_FlReactor</CODE> only available if ACE
- was compiled with support for the XWindows Toolkit
- </TD></TR>
- <TR><TD><CODE>WFMO<CODE></TD><TD>Use the
- <CODE>ACE_WFMO_Reactor</CODE> only available on
- Win32 platforms.
- </TD></TR>
- <TR><TD><CODE>MsgWFMO<CODE></TD><TD>Use the
- <CODE>ACE_Msg_WFMO_Reactor</CODE> only available on
- Win32 platforms.
- </TD></TR>
- </TABLE>
- The default is <code>select_mt</code></TD></TR>
+(<em>which</em> = <code>null</code>). Default is <code>token</code></TD></TR>
<TR>
<TD><CODE>-ORBcoltable</CODE> <EM>which</EM></TD>
<TD><a name="-ORBcoltable"></a>Specify whether each ORB uses a global
@@ -268,7 +240,7 @@ copied instead of appended to the CDR stream.</TD></TR>
Though <CODE>tss</CODE> should give the
optimal performance;
we made the default <CODE>global</CODE>.
- TAO optimizations for octet sequences will not work when
+ TAO optimizations for octet sequences will not work when
returning that data type if the allocator is
<CODE>tss</CODE>.
Using global allocator also allows the users to
@@ -420,35 +392,10 @@ This makes sense in case of optiziations and is allowed when
no forwarding is used or only a single threaded client.
</TD></TR>
<TR>
-<TD><CODE>-ORBclientconnectionhandler</CODE> <EM>MT / ST / RW</EM></TD>
-
-<TD><A name="-ORBclientconnectionhandler"></a>
-
-ST means use the single-threaded client connection handler, i.e., the
-leader follower model will not be used. However, ST does support
-nested upcalls and handling of new requests while waiting for the
-reply from a server. <p>
-
-MT means use the multi-threaded client connection handler which uses
-the leader follower model. This model allows the use of multiple
-threads with a single Reactor. <p>
-
-RW selects a strategy that simply blocks in recv() when waiting for a
-response from the server instead of waiting in the Reactor. The RW
-strategy only works when the application does not have to worry about
-new request showing up when waiting for a response. Therefore, this
-strategy is appropriate only for "pure" clients. Note that
-applications with nested upcalls are not "pure" clients. Also note
-that this strategy will only effect two way calls, since there is no
-waiting for one way calls. This strategy can also be used in an
-application that is both a client and a server if the server side is
-handled by a separate thread and the client threads are "pure"
-clients. <p>
-
-Default for this option is MT.
-
-</TD></TR>
-
+<TD><CODE>-ORBclientconnectionhandler</CODE> <EM>MT / ST</EM></TD>
+<TD><A name="-ORBclientconnectionhandler"></a> ST means use the
+single-threaded client connection handler and MT means use the
+multi-threaded client connection handler .</TD></TR>
</TABLE>
</P>
</BLOCKQUOTE>