summaryrefslogtreecommitdiff
path: root/TAO/examples/POA/Forwarding/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/examples/POA/Forwarding/README')
-rw-r--r--TAO/examples/POA/Forwarding/README11
1 files changed, 7 insertions, 4 deletions
diff --git a/TAO/examples/POA/Forwarding/README b/TAO/examples/POA/Forwarding/README
index 938f2a974f5..0acbf8615f6 100644
--- a/TAO/examples/POA/Forwarding/README
+++ b/TAO/examples/POA/Forwarding/README
@@ -13,12 +13,12 @@ Where every third request is a forwarding request to the object.
Here's an example for 5 requests:
-first call (request no 1)
+first call (request no 1)
second call (request no 2)
forwarding call (request no 3)
thrid call (request no 4)
fourth call (request no 5)
-(no six would be a forwarding call again)
+(no six would be a forwarding call again)
Two types of location forwardings are implemented: (1) the POA
approach and (2) the servant locator approach. Both are mentioned in
@@ -35,12 +35,12 @@ follows (basically just the switches are different):
% server -p server2 -ORBobjrefstyle url
% server -g server2 -p server1 -ORBobjrefstyle url
-% client -f server1 -i 5
+% client -g server1 -i 5
For additional features try using the first server with the POA
apporach and the second with the servant locator approach:
-% server -o server3 -ORBobjrefstyle url
+% server -o server3 -ORBobjrefstyle url
% server -g server3 -p server2 -ORBobjrefstyle url
% server -f server2 -o server1 -ORBobjrefstyle url
% client -f server1 -i 8
@@ -50,3 +50,6 @@ forwarding is called on this one and the next two calls are going to
be called on the second one. Location forwarding is then called on
the second one and the last two calls are then done on the thrid
server.
+
+
+