summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDwayne Boone <dwayne@zeroc.com>2007-01-16 13:37:58 +0000
committerDwayne Boone <dwayne@zeroc.com>2007-01-16 13:37:58 +0000
commit63def25e65ff486d247b15e79b46b719b5b426cf (patch)
tree709737d18199b81f55c7a5e527075372e9a4a82f
parentExpanmded comment (diff)
downloadice-63def25e65ff486d247b15e79b46b719b5b426cf.tar.bz2
ice-63def25e65ff486d247b15e79b46b719b5b426cf.tar.xz
ice-63def25e65ff486d247b15e79b46b719b5b426cf.zip
Expanded comment
-rw-r--r--cpp/demo/Ice/hello/README15
-rw-r--r--java/demo/Ice/hello/README3
-rw-r--r--py/demo/Ice/hello/README3
-rw-r--r--rb/demo/Ice/hello/README3
-rw-r--r--vb/demo/Ice/hello/README3
5 files changed, 17 insertions, 10 deletions
diff --git a/cpp/demo/Ice/hello/README b/cpp/demo/Ice/hello/README
index cf79f825151..6e8f4ed3476 100644
--- a/cpp/demo/Ice/hello/README
+++ b/cpp/demo/Ice/hello/README
@@ -1,6 +1,5 @@
-This demo illustrates how to invoke ordinary (twoway)
-operations, as well as how to make oneway, datagram,
-secure, and batched invocations.
+This demo illustrates how to invoke ordinary (twoway) operations, as
+well as how to make oneway, datagram, secure, and batched invocations.
To run the demo, first start the server:
@@ -10,6 +9,10 @@ In a separate window, start the client:
$ client
-To test timeouts you can use 'T' to set a timeout on
-the client proxy and 'P' to set a delayed response in
-the server to cause a timeout.
+To test timeouts you can use 'T' to set a timeout on the client proxy
+and 'P' to set a delayed response in the server to cause a timeout.
+You will notice that two "Hello World!" messages will be printed by the
+server in this case. This is because the sayHello method is marked as
+idempotent in the slice, meaning that Ice does not need to follow the
+at-most-once retry semantics. See manual for more information about
+retry behavior.
diff --git a/java/demo/Ice/hello/README b/java/demo/Ice/hello/README
index 6c5a5e52a8c..87a281d58a6 100644
--- a/java/demo/Ice/hello/README
+++ b/java/demo/Ice/hello/README
@@ -14,4 +14,5 @@ and 'P' to set a delayed response in the server to cause a timeout.
You will notice that two "Hello World!" messages will be printed by the
server in this case. This is because the sayHello method is marked as
idempotent in the slice, meaning that Ice does not need to follow the
-at-most-once retry semantics.
+at-most-once retry semantics. See manual for more information about
+retry behavior.
diff --git a/py/demo/Ice/hello/README b/py/demo/Ice/hello/README
index ac06c7cfebc..aebda51f1df 100644
--- a/py/demo/Ice/hello/README
+++ b/py/demo/Ice/hello/README
@@ -14,4 +14,5 @@ and 'P' to set a delayed response in the server to cause a timeout.
You will notice that two "Hello World!" messages will be printed by the
server in this case. This is because the sayHello method is marked as
idempotent in the slice, meaning that Ice does not need to follow the
-at-most-once retry semantics.
+at-most-once retry semantics. See manual for more information about
+retry behavior.
diff --git a/rb/demo/Ice/hello/README b/rb/demo/Ice/hello/README
index c2874ea191a..0c58f830419 100644
--- a/rb/demo/Ice/hello/README
+++ b/rb/demo/Ice/hello/README
@@ -14,4 +14,5 @@ and 'P' to set a delayed response in the server to cause a timeout.
You will notice that two "Hello World!" messages will be printed by the
server in this case. This is because the sayHello method is marked as
idempotent in the slice, meaning that Ice does not need to follow the
-at-most-once retry semantics.
+at-most-once retry semantics. See manual for more information about
+retry behavior.
diff --git a/vb/demo/Ice/hello/README b/vb/demo/Ice/hello/README
index 105bc28000a..e7409cebc5c 100644
--- a/vb/demo/Ice/hello/README
+++ b/vb/demo/Ice/hello/README
@@ -14,4 +14,5 @@ and 'P' to set a delayed response in the server to cause a timeout.
You will notice that two "Hello World!" messages will be printed by the
server in this case. This is because the sayHello method is marked as
idempotent in the slice, meaning that Ice does not need to follow the
-at-most-once retry semantics.
+at-most-once retry semantics. See manual for more information about
+retry behavior.