R. Clayton (rclayton@monmouth.edu)
(no date)
I'm testing Project 1a, and I have a few tips for you to get right on Project
1b:
* The name of the client is "clnt" and the name of the server is "srvr". The
names of the client and server are not, for example, "CorralClient.class"
and "CorralServer.class", or "corl_clnt.o" and "corral_svr.o", or "c1.class"
and "s1.class".
Those of you writing java code have a bit of a problem, but it's not
insurmountable: the class names are "clnt.class" and "srvr.class". If your
java sensibilities are offended by lower-case letters, then you can call
them "Clnt.class" and "Srvr.class".
* They're called "command-line options" because they can optionally appear on
the command line. I should be able to run your programs without incident by
typing "./srvr" and "./clnt". Also, both "./srvr -hlocalhost" and "./srvr
-p5370" should work.
Command-line options are usually not ordered. both "./srvr -p5370
-hlocalhost" and ./srvr -hlocalhost -p5370" should work.
Also, as demonstrated by the previous examples there is no space between the
option and its value (actually, the space should be optional; both "-p5370"
and "-p 5370" should work). However, by majority vote, from now on option
values should be separated from their options by space.
If you're writing C or C++ code, you should look at the getopt man page
(type "man -S3 getopt" on rockhopper). If you're writing Java code, google
for "java command-line options" for a plethora of libraries.
This archive was generated by hypermail 2.0b3 on Tue Apr 06 2004 - 13:30:06 EDT