diff options
| author | Johnny Willemsen <jwillemsen@remedy.nl> | 2006-04-20 12:40:50 +0000 |
|---|---|---|
| committer | Johnny Willemsen <jwillemsen@remedy.nl> | 2006-04-20 12:40:50 +0000 |
| commit | 1939a15774cacdf268c47b0bd7eb851ca4f149ab (patch) | |
| tree | 8eaa757e26eff9e7ac20b3083429ff45aa4faefb /TAO/docs | |
| parent | 2f8a860d14adb56c57241b6e76a665e3835b1d04 (diff) | |
| download | ATCD-1939a15774cacdf268c47b0bd7eb851ca4f149ab.tar.gz | |
ChangeLogTag: Thu Apr 20 11:50:12 UTC 2006 Johnny Willemsen <jwillemsen@remedy.nl>
Diffstat (limited to 'TAO/docs')
| -rw-r--r-- | TAO/docs/Options.html | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/TAO/docs/Options.html b/TAO/docs/Options.html index 57af57ec155..c5151b03d56 100644 --- a/TAO/docs/Options.html +++ b/TAO/docs/Options.html @@ -326,6 +326,12 @@ current message block contains enough space for it -- the octet sequence is copied instead of appended to the CDR stream. </td> </tr> <tr> + <td><code>-ORBMaxMessageSize</code> <em>maxsize</em></td> + <td><a name="-ORBMaxMessageSize"></a>Set maximum size of + outgoing GIOP request/reply. The request or reply + being sent will be fragmented, if necessary.</td> + </tr> + <tr> <td><code>-ORBCollocation</code> <em>global/per-orb/no</em></td> <td><a name="-ORBCollocation"></a>Specifies the use of collocation object optimization. If <code>global</code> is specified @@ -1373,7 +1379,7 @@ allowed when no forwarding is used or only a single threaded client. </td> </em> </td> <td><em>Please note that these two options are synonymous and can be used interchangeably.</em> - <p><a name="-ORBClientConnectionHandler"></a><em>ST</em> means + <p><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 nested upcalls and handling of new requests while waiting for the reply @@ -1387,7 +1393,7 @@ instead of waiting in the Reactor using the Leader/Followers pattern. The <em>RW</em> strategy only works when the application does not have to worry about new request showing up when waiting for a response. Further, this strategy cannot be used with Asynchronous -Method Invocation (AMI) calls and when using BiDIR GIOP. +Method Invocation (AMI) calls and when using BiDIR GIOP. Therefore, this strategy is appropriate only for "pure" synchronous clients. Note that applications that require nested upcalls are not "pure" synchronous clients. Also note that this @@ -1424,13 +1430,13 @@ I'm not sure what the affect of AMI on this option is. effect of registering and unregistering the connection handlers with the Reactor for every invocation, which has a negative impact on performance. Setting the option to <em> 0 - </em> prevents this performance impact but leads to problems - outlined + </em> prevents this performance impact but leads to problems + outlined <A href="http://deuce.doc.wustl.edu/bugzilla/show_bug.cgi?id=2186"> here</A> and <a href="http://deuce.doc.wustl.edu/bugzilla/show_bug.cgi?id=2224"> - here</A> + here</A> <p>Default for this option is <em>0</em>. </p> </td> </tr> |