perfsonar development work

Author: zurawski
Date: 2006-08-11 12:37:29 -0400 (Fri, 11 Aug 2006)
New Revision: 1551

Modified:
   branches/release/perfsonar/releng/perfSONAR-1.0/Readme.txt
Log:
Added references to the perl client.

-jason



Modified: branches/release/perfsonar/releng/perfSONAR-1.0/Readme.txt
===================================================================
--- branches/release/perfsonar/releng/perfSONAR-1.0/Readme.txt  2006-08-11 
16:23:36 UTC (rev 1550)
+++ branches/release/perfsonar/releng/perfSONAR-1.0/Readme.txt  2006-08-11 
16:37:29 UTC (rev 1551)
@@ -780,7 +780,7 @@
                MA to store, the last 2 tests will simply f-
                ail and pass back an error message.
 
-       The actual client is located in the package:
+       The actual java client is located in the package:
        
                org.perfsonar.client.testHarness.SOAPClient
 
@@ -792,13 +792,28 @@
        java org.perfsonar.client.testHarness.SOAPClient \
 URL INFILE.xml OUTFILE.xml
 
+       Where:
+               URL = http://$HOST:$PORT/$SERVICE
+               
+               INFILE.xml = One of the example requests fr-
+                            om the xml/ directory.
+       
+               OUTFILE.xml = Newly created response
+
        Errors indicating the class file cannot be found are
        more than likely related to the CLASSPATH.
        
        The test scripts we install include a fabricated 
        CLASSPATH to ensure the tests work; don't let this 
        stop you from changing the CLASSPATH on your own.
+
+       An additional client written in perl is available in
+       the 'contrib' package which can be optionally insta-
+       lled.  To invoke this client:
        
+               $PERFSONAR/contrib/client/./client.pl URL \
+INFILE.XML
+       
 ------------------------------------------------------------
 4) Problems
 ------------------------------------------------------------