NDT-DEV email list created

Revision: 310
Author: sspeery
Date: Tue Mar  9 06:08:22 2010
Log: Edited wiki page through web user interface.
Seth made typographical edits in "Java Security Warning" section, reverted  
the "Protocol Error" section to reflect the deletion of more verbose  
messages, and added a bit more clarification on the "Server Process not  
Running" section.
http://code.google.com/p/ndt/source/detail?r=310

Modified:
 /wiki/WarningsAndMessages.wiki

=======================================
--- /wiki/WarningsAndMessages.wiki      Tue Mar  9 05:49:54 2010
+++ /wiki/WarningsAndMessages.wiki      Tue Mar  9 06:08:22 2010
@@ -8,19 +8,19 @@

 == Java Security Warning for Tcpbw100 - The application's digital  
signature has been verified. Do you want to run the application? ==

-NDT uses a signed-Java client applet Tcpbw100 signed by the New America  
Foundation, a partner in Measurement Lab.  By signing the NDT client, the  
user is assured that the that will run is the code that was released by  
Measurement Lab.  The certificate is required by some NDT integrators.   
Some earlier versions of the Sun Java Runtime Environment will not display  
a warning when encountering NDT, and the most up-to-date versions will.   
Users encountering a security warning should choose "Run" to allow NDT to  
run normally.
+NDT uses a signed-Java client applet Tcpbw100 signed by the New America  
Foundation, a partner in Measurement Lab.  By signing the NDT client, the  
user is assured that the code that will run is the code that was released  
by Measurement Lab.  The certificate is required by some NDT integrators.   
Some earlier versions of the Sun Java Runtime Environment will not display  
a warning when encountering NDT, but the most up-to-date versions will.   
Users encountering a security warning should choose "Run" to allow NDT to  
run normally.

 == NDT message - Another client is currently being served, your test will  
begin within NNN seconds ==

 NDT may handle multiple tests, but during very busy times, NDT may queue a  
small amount of newly arriving tests so that it can adequately serve tests  
that are already in progress.  Those newly arriving tests will get the  
above message and will begin shortly.  Users receiving this warning should  
either wait or test later.

-== Protocol error! or Protocol error!  expected XXXX got YYYY instead or  
Error in parsing test results! ==
-
-As part of testing, the NDT client and server are expected to have a  
scripted conversation.  This message from the client indicates that the  
client received results, messages or conditions that was unexpected.  Users  
receiving this message once should simply try again. If the condition  
persists, it may indicate a problem that NDT is unable to interpret.   
Reproducible occasions resulting in these messages should be reported to  
the NDT developers.
+== Protocol error! ==
+
+As part of testing, the NDT client and server are expected to have a  
scripted conversation.  This message from the client indicates that the  
client received results, messages or conditions that were unexpected.   
Users receiving this message once should simply try again. If the condition  
persists, it may indicate a problem that NDT is unable to interpret.   
Reproducible occasions resulting in these messages should be reported to  
the NDT developers.

 == Server process not running: start web100srv process on remote server ==

-NDT client needs to connect to port 3001 of the server.  If an attempt to  
connect to that port is not answered or is otherwise refused, the above  
message is displayed.  The message is a reminder to server operators to  
start the service.  Other users receiving this message should consider  
whether they are behind a security firewall that is configured to block  
outbound TCP connections to port 3001 (this will not be the case for most  
residential users).  If the condition persists, it may also be the case  
that the testing server is temporarily unavailable due to a network or  
server outage.
+NDT client needs to connect to port 3001 of the server.  If an attempt to  
connect to that port is not answered or is otherwise refused, the above  
message is displayed.  The presence of a firewall that blocks ports 3001,  
3002, 3003 and/or 7123, or the presence of a proxy server anywhere between  
the client and server will trigger this message.  In normal operating  
conditions (that is, an unblocked communications pathway between client and  
server), the message is intended to serve as a reminder to server operators  
to start the service.  If you receive this message, you should consider  
whether you are behind a proxy server or a security firewall that is  
configured to block outbound TCP connections to port 3001.  While this will  
not be the case for most residential users, it may be more common for  
businesses and larger organizations.  If there is found to be no proxy  
server or firewall on the path between your computer and the server, yet  
the condition persists, it may be the case that the testing server is  
temporarily unavailable due to a network or server outage.

 == Server Busy: Too many clients waiting in server queue. Please try again  
later. ==

@@ -33,4 +33,3 @@
 == Last Updated ==

 $Id$
-