diff options
Diffstat (limited to 'TAO/docs/Options.html')
| -rw-r--r-- | TAO/docs/Options.html | 25 |
1 files changed, 2 insertions, 23 deletions
diff --git a/TAO/docs/Options.html b/TAO/docs/Options.html index baa2dc38466..45077a56964 100644 --- a/TAO/docs/Options.html +++ b/TAO/docs/Options.html @@ -207,7 +207,7 @@ same host: % NameService.exe -ORBEndpoint iiop://localhost:12345 </code></p> <p><code> -% client.exe -ORBInitRef NameService=iiop://localhost:12345 +% client.exe -ORBInitRef NameService=iiop://localhost:12345" </code></p> <p>An explanation of these command-line options appears below. </p> <p></p> @@ -909,11 +909,6 @@ the ORB uses. The default reactor is the ACE_TP_Reactor. <td><code>tp</code></td> <td>Use the <code>ACE_TP_Reactor</code>, a select based thread-pool reactor which is the - MT_NO_UPCALL means use a client connection handler that - participates in the leader-follower model like MT, but, like - RW, does not allow handling of nested upcalls within the - waiting thread. - default.</td> </tr> </tbody> @@ -1173,11 +1168,7 @@ a null lock is used. This makes sense in case of optimizations 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 - / MT_NOUPCALL</em><br> - <code>-ORBWaitStrategy</code> <em>MT / ST / RW / MT_NOUPCALL - </em> -</td> + <td><code>-ORBClientConnectionHandler</code> <em>MT | ST | RW</em></td> <td><a name="-ORBClientConnectionHandler"></a><em>ST</em> means use the single-threaded client connection handler, i.e., the leader follower model will not be used. However, <em>ST</em> does support @@ -1198,18 +1189,6 @@ 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> -<p> - MT_NOUPCALL means use a client connection handler that - participates in the leader-follower model like MT, but, like - RW, does not allow handling of nested upcalls within the - waiting thread. Note that with this strategy it is possible - to "run out of threads" in a thread pool, and that TAO doesn't - grow thread pools. Unlike RW, this does not require <a - href="-ORBTransportMuxStrategy">-ORBTransportMuxStrategy <em>EXCLUSIVE</em></a>. -<!-- -I'm not sure what the effect of AMI on this option is. ---> -</p> <p>Default for this option is <em>MT</em>. </p> </td> </tr> |