The procedure for compiling and linking the client and the server is described in the excellent README file that comes with the software. For convenience here is a summary. If you are using a unix machine, you should do the following:

• create a directory for the experiment, say exp5.1.

• place CNAI.api.tar in that directory.

• cd to the directory exp5.1.

• type "tar xvf CNAI.api.tar".

• cd to either compile_linux or compile_solaris.

• type "make echoclient".

• echoclient is now in the compile_xxx directory.

In my own experience echo service is not quite "standard throughout the internet". In the name of security many network administrators have turned off what they regard as non-essential services. Often this includes echo service. To test your echo client use cs.purdue.edu.

The Optional Extensions are quite interesting. The second is easier requiring only a forever loop (for testing it might be more convenient to use a for loop to handle a small number of connections). You just have to figure out where to put it.

The first is only slightly harder. You have to open a file, repeatedly write whatever comes in to that file, and eventually close the file.

You now have a working echo client and server so you might as well experiment. Try connecting from two different machines at the same time. Execute your server, execute a client, and execute a client from a different host (or window). Notice the behavior of the server as it gets intermingled messages from two hosts. Examine the log file to verify that the observed behavior is reflected in the log. Now figure out why this somewhat unexpected behavior.

---

This site is maintained by by W. David Laverell of the Computer Science Department at Calvin College.
For assistance or corrections, please contact him at lave@calvin.edu.