NDT-DEV email list created

Revision: 662
Author:   

Date:     Fri Sep 30 02:32:55 2011
Log:      Added a basic test sessions descriptions.
http://code.google.com/p/ndt/source/detail?r=662

Modified:
 /wiki/NDTArchitecture.wiki

=======================================
--- /wiki/NDTArchitecture.wiki  Fri Sep 30 02:10:26 2011
+++ /wiki/NDTArchitecture.wiki  Fri Sep 30 02:32:55 2011
@@ -40,7 +40,7 @@
 The brief information about each of the NDT component can be found in the  
following table. All sources locations are relative to the root of the  
checked out sources from the code repository.

 || *Component Name* || *Type* || *Description* || *Sources Location* ||
-|| *web100clt* || Client Tools || The NDT Client application. || *src*  
<br/><br/> {{{web100clt.c network.c usage.c logging.c utils.c protocol.c  
test_sfw_clt.c test_mid_clt.c test_c2s_clt.c test_s2c_clt.c  
test_meta_clt.c}}} ||
+|| *web100clt* || Client Tools || The NDT Client application (used from  
command line). || *src* <br/><br/> {{{web100clt.c network.c usage.c  
logging.c utils.c protocol.c test_sfw_clt.c test_mid_clt.c test_c2s_clt.c  
test_s2c_clt.c test_meta_clt.c}}} ||
 || *Tcpbw100.jar* || Server/Client Tools || The Java Applet-based client  
that requires JVM browser plugin installed at the client machine. ||  
*Applet* <br/><br/> {{{Tcpbw100.java}}}||
 || *web100srv* || Server Tools || The NDT Server application. || *src*  
<br/><br/> {{{web100srv.c web100-util.c web100-pcap.c web100-admin.c  
network.c usage.c utils.c mrange.c logging.c testoptions.c protocol.c  
test_sfw_srv.c test_meta_srv.c ndt_odbc.c}}} ||
 || fakewww || Server Tools || Optional 'lite' web server. || *src*  
<br/><br/> {{{fakewww.c troute.c troute6.c tr-tree.c tr-tree6.c network.c  
usage.c logging.c}}} ||
@@ -53,4 +53,37 @@

 == Life Cycle ==

+The NDT client and server interaction details can be found in the  
[NDTProtocol#Protocol_description NDT Protocol description].
+
+=== Test session with the Java Applet-based client ===
+
+A basic NDT test session with the Java Applet-based client looks as  
following:
+
+*TODO - add a basic flow chart for the NDT session with a federated  
fakewww*
+
+ # The process starts with the user opening a browser and entering the NDT  
server URL
+   * An optional step is to point to a well known server and accept a  
redirect message (Federated mode)
+   * Otherwise the URL points to the NDT server itself (either an apache  
web server or the fakewww process answer the request)
+ # The web server responds by returning the page, with an embedded java  
applet (class or jar file)
+ # The user must manually request a test be performed by clicking the  
“start” button
+ # The applet opens a connection back 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 client to control  
the client’s actions and synchronize the start of the various tests. The  
server and the client negotiate the test suite.
+ # The NDT client and the NDT server performs the negotiated test suite.  
The client opens new data channels back to the server for testing purposes.  
Allowing the client to open connections makes it easy to get past  
client-side firewall boxes.
+ # The server extracts the Web100 data and analyzes the connection for  
faults.
+ # The results are recorded in the servers’ log file and the results are  
returned to the client for display to the user.
+
+=== Test session with the web100clt client ===
+
+A basic NDT test session with the web100clt client looks as following:
+
+*TODO - add a basic flow chart for the NDT session with web100clt*
+
+ # The process starts with connecting to the server's testing engine  
(web100srv process) by the web100clt client.
+ # 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 client to control  
the client’s actions and synchronize the start of the various tests. The  
server and the client negotiate the test suite.
+ # The NDT client and the NDT server performs the negotiated test suite.  
The client opens new data channels back to the server for testing purposes.  
Allowing the client to open connections makes it easy to get past  
client-side firewall boxes.
+ # The server extracts the Web100 data and analyzes the connection for  
faults.
+ # The results are recorded in the servers’ log file and the results are  
returned to the client for display to the user.
+
 == Build Instructions ==