diff options
| author | Johnny Willemsen <jwillemsen@remedy.nl> | 2006-04-03 18:31:14 +0000 |
|---|---|---|
| committer | Johnny Willemsen <jwillemsen@remedy.nl> | 2006-04-03 18:31:14 +0000 |
| commit | bb0d7f2681c2157f7461a0699b92b8d0fdbee8f8 (patch) | |
| tree | bbc7f087edd85df9c32718aa2606c688b46d6f25 | |
| parent | c4c46f9f5775935a82deab0983424912ae603203 (diff) | |
| download | ATCD-bb0d7f2681c2157f7461a0699b92b8d0fdbee8f8.tar.gz | |
ChangeLogTag: Mon Apr 3 15:15:12 2006 Johnny Willemsen <jwillemsen@remedy.nl>
| -rw-r--r-- | TAO/docs/Options.html | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/TAO/docs/Options.html b/TAO/docs/Options.html index 348ff6de5e3..57af57ec155 100644 --- a/TAO/docs/Options.html +++ b/TAO/docs/Options.html @@ -1387,7 +1387,8 @@ 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. Therefore, this strategy is appropriate +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 strategy will only affect two way calls, since there is no waiting for |