Program Assignment 5: Network Communication Solution

Description

1. Purpose

This assignment focuses on network communication via TCP/IP and sockets. In this assignment you will implement in Java the DateServer/DateClient pair found in the OS textbook – Figures 3.27 and 3.28, respectively. You will then modify them to run within ThreadOS. Finally, you will modify the functionality according to specifications detailed below, while adding a primitive handshake capability akin to that described in 19.3.2.

2. Sockets

Recall that a socket is defined as an endpoint for communication. A pair of processes communicating over a network employs a pair of sockets—one for each process. Remember also that a socket is simply an IP address concatenated with a port number. In general, sockets use a client–server architecture. The server waits for incoming client requests by listening to a specified port. Once a request is received, the server accepts a connection from the client socket to complete the connection. We will explore this capability through making modifications in the basic functionality delivered in the text’s DateServer and DateClient source files.

3. Statement of Work

Part 1: Implement DateServer (Figure 3.27) and DateClient.java (Figure 3.28)on ThreadOS

Put a fresh copy of ThreadOS from the normal location

(/opt/java/libs/cleanTOS/) into ~/TOS/. As usual, create a working directory in ~/src/java/prog5 and link to the class files in ~/TOS/.

Convert DateServer.java and DateClient.java to run within ThreadOS. Note that in lieu of using the host string “127.0.0.1”, you can use the string “localhost” if you find that more readable. You will also need to modify DateServer.java so that it connects to a random port (ServerSocket(0)) rather than a static port and prints out the port where it is listening. This will prevent interference with other students’ testing. Along that same line, you will need modify DateClient.java so that it accepts a parameter to specify the port to which to connect, which should be specified at runtime to match the port DateServer printed out.

Test that your conversion works by:

javac *.java # only DateServer.java and DateClient.java should be present java Boot

12. Shell DateServer &

DateClient <port number from DateServer output> exit

q

Note that your code should allow you to “exit” cleanly from the Shell and to “q” out of ThreadOS. You may note a delay with the command prompt between “DateServer &” and “DateClient”, but this is merely because DateServer is asked to run in the background, so output may get intermixed. Hitting <Enter> will get you a clean prompt.

Part 2: Create CmdServer.java and CmdClient.java

You will now be expected to create your own server and client, based on the previous code. To start:

cp DateServer.java CmdServer.java # use DateServer as basis for CmdServer

cp DateClient.java CmdClient.java # use DateClient as basis for CmdClient

Next, edit CmdServer.java and CmdClient.java to accomplish the following functionality. Test incrementally to make the overall task more achievable.

1. Change the port for initiating communication between the server and the client.

1. 1. For CmdServer, have the server loop through ports in the range 5000 – 5500, inclusive. Once it successfully listens on a port, have it print out a message detailing its hostname and listening port. It will look something like this:

2. Modify client to transmit a message entered by the user. Modify server to accept the message, reverse the text, and send it back to the client. Client should print the reversed text once received.

3. Establish a “handshake” for primitive authentication.

2. 1. After connection, the first thing the client is to transmit is the username of the client’s owner.

1. 2. The server should check its first received message against its own username to ensure they match. If they do not match, the server should disconnect and exit. Client should check for a response (which should be the new random port—see c. below), but if receiving a “null”, client should exit.

1. 2. You may test the username handshake by (temporarily) having the client send an incorrect username to verify the server detects this, and that disconnects and exits are accomplished appropriately.

1. 2. Server then should open a new random port (ServerSocket(0)) and transmit this new port to the client.

1. 2. Client should then connect to the new port received from the server and be ready for user input.

4. Modify client to disconnect and exit if the message entered by the user is “bye” or “die”. Also modify the server to close the connection and accept new connections (with handshaking) after receiving a “bye” message, and to gracefully exit entirely after receiving a “die” message.

4. Modify server to check the message received, and if it is one of the following commands, instead execute the command locally and then transmit the results to the client. Note that the commands should be able to run with parameters, but do not worry about properly parsing and executing wildcards. Further, note that all previous functionality should continue to function.

4. 1. “whoami”

   2. “ls”

4. 3. “pwd”

   4. “ps”

4. 5. “man”

   6. “echo”

   7. “date”

4. What to Turn In

Softcopy (file uploads according to your Blackboard Assignment):

1. Part 1:

1. 15. DateServer.java and DateClient.java

2. Part 2: CmdServer.java and CmdClient.java

1. 15. Sample output executing the following commands:

       • java Boot

       • l Shell

       • CmdServer &

       • CmdClient <port number>

1. 15. • Hello

       • whoami

       • date

       • bye

       • CmdClient

       • Hello again

1. 15. • echo Hello again

       • ls

       • ls -l

       • ps ux

       • man pkill

       • die

1. 15. • exit

       • q

5. FAQ and Grade Guide

As this is a new assignment, a FAQ will be posted on Blackboard and updated as needed. 🙂