ndt-dev - [ndt-dev] [ndt] r714 committed - Clarification text
Subject: NDT-DEV email list created
List archive
- From:
- To:
- Subject: [ndt-dev] [ndt] r714 committed - Clarification text
- Date: Tue, 11 Oct 2011 20:03:17 +0000
Revision: 714
Author:
Date: Tue Oct 11 13:02:28 2011
Log: Clarification text
http://code.google.com/p/ndt/source/detail?r=714
Modified:
/wiki/NDTArchitecture.wiki
=======================================
--- /wiki/NDTArchitecture.wiki Tue Oct 11 12:56:02 2011
+++ /wiki/NDTArchitecture.wiki Tue Oct 11 13:02:28 2011
@@ -53,7 +53,7 @@
http://ndt.googlecode.com/svn/wiki/NDTArchitecture.images/NDT_flow_2.png
# The process starts with the user specifying a known NDT server for the web100clt client to connect to.
- * Unlike in the Applet client scenario, the only way to redirect the web100clt client is to use a DNS-based solution like [http://donardns.org/ DONAR].
+ * Unlike in the Applet client scenario, the web100clt does not support redirection so, unless a DNS-based solution like [http://donardns.org/ DONAR] is employed, the user must direct the client to a specific NDT server.
# The web100clt client connects to the server's testing engine (web100srv process).
# A child process is created to handle the test and the parent goes back to listening for more test requests. The parent keeps a FIFO queue to process multiple requests.
# A control channel is created between the server and the client to control the client’s actions and synchronize the start of the various tests. The server and the client negotiate the test suite.
- [ndt-dev] [ndt] r714 committed - Clarification text, ndt, 10/11/2011
Archive powered by MHonArc 2.6.16.