Skip to Content.
Sympa Menu

ndt-dev - [ndt-dev] [ndt] r674 committed - Fixed in the life cycle section.

Subject: NDT-DEV email list created

List archive

[ndt-dev] [ndt] r674 committed - Fixed in the life cycle section.


Chronological Thread 
  • From:
  • To:
  • Subject: [ndt-dev] [ndt] r674 committed - Fixed in the life cycle section.
  • Date: Mon, 03 Oct 2011 09:57:50 +0000

Revision: 674
Author:

Date: Mon Oct 3 02:56:54 2011
Log: Fixed in the life cycle section.
http://code.google.com/p/ndt/source/detail?r=674

Modified:
/wiki/NDTArchitecture.wiki

=======================================
--- /wiki/NDTArchitecture.wiki Sun Oct 2 04:23:48 2011
+++ /wiki/NDTArchitecture.wiki Mon Oct 3 02:56:54 2011
@@ -68,10 +68,10 @@
# 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.
+ # 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.
# 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.
+ # The results are recorded in the [NDTDataFormat#web100srv.log_file servers’ log file] and the results are returned to the client for display to the user.

=== Test session with the web100clt client ===

@@ -81,10 +81,10 @@

# 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.
+ # 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.
# 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.
+ # The results are recorded in the [NDTDataFormat#web100srv.log_file servers’ log file] and the results are returned to the client for display to the user.

== Build Instructions ==



  • [ndt-dev] [ndt] r674 committed - Fixed in the life cycle section., ndt, 10/03/2011

Archive powered by MHonArc 2.6.16.

Top of Page