From 6e605e1190bf6e170d5b586e6dec24b034bc46cb Mon Sep 17 00:00:00 2001 From: yang-g Date: Thu, 30 Jul 2015 11:42:38 -0700 Subject: resolve comments --- doc/connection-backoff-interop-test-description.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/connection-backoff-interop-test-description.md b/doc/connection-backoff-interop-test-description.md index d493900666..0f00c86dca 100644 --- a/doc/connection-backoff-interop-test-description.md +++ b/doc/connection-backoff-interop-test-description.md @@ -29,7 +29,7 @@ Clients should accept these arguments: * --server_control_port=PORT * The server port to connect to for rpc. For example, "8080" * --server_retry_port=PORT - * The server port to connect to for testing backoffs. For example, "8080" + * The server port to connect to for testing backoffs. For example, "8081" The client must connect to the control port without TLS. The client should either assert on the server returned backoff status or check the returned @@ -53,7 +53,8 @@ Server A C++ server can be used for the test. Other languages do NOT need to implement a server. To minimize the network delay, the server binary should run on the -same machine with the client binary. +same machine or on a nearby machine (in terms of network distance) with the +client binary. A server implements the ReconnectService to its state. It also opens a tcp server on the retry_port, which just shuts down all incoming tcp @@ -72,5 +73,5 @@ The server accepts these arguments: * --control_port=PORT * The port to listen on for control rpcs. For example, "8080" * --retry_port=PORT - * The tcp server port. For example, "8080" + * The tcp server port. For example, "8081" -- cgit v1.2.3