You are asked to implement a client-server-based Internet application.

The server is similar to the daytime server except that it is a "parking availability in Education Car Park" server. Your implementation does not need to report the actual number of parking spaces in the actual Education Car Park; the number of available parking spaces always starts at 20.

A client can connect to the server and make one of two different requests:

1. ask: The client can ask for the number of available parking spaces. The server responds with an appropriate string, like: "Education Car Park has 20 spaces available." Your string should look exactly like this string, except the number "20" should be the correct number. Asking for the number of available parking spaces does not change the count of available spaces.

2. reserve: The client can ask to reserve a parking space. If a space is available, the server subtract one parking spot count and responds with an appropriate string, like: "Space Reserved. Education Car Park now has 19 spaces available." Your string should look exactly like this string, except the number "19" should be the correct number. If there is no space available (i.e., the count is already zero), then your server should respond with "Failed Reservation."

For this simplified server, there is no way to release a parking space and increase the count. Note that the 3 possible messages above are of variable length.

The server should be runnable from the command line with:

unix-prompt% edmts.server

and it should print out the IP address of the machine it is running on and port number it is listening on. See my example program in getIPAddress.c. For example, something li  ke:

EDMTS is running on 129.128.4.80, listening on port 24459

If your Unix machine (e.g., Linux under virtual machine) is causing your server problems with respect to the IP address of the server's machine, it is OK to print:

EDMTS is running on local host, listening on port 24459

and then to have the user find the actual IP address of the server/local machine using Unix's ifconfig command.

Each time that the server starts, it considers 20 spaces to be available.

The client should be runnable from the command line with either:

unix-prompt% edmts.client 129.128.4.80 24459 ask

or

unix-prompt% edmts.client 129.128.4.80 24459 reserve

since, of course, the client needs to know the well-known location of the server process (i.e., both IP address and port number).

If called with the "ask" command-line argument, the client will just ask the server for the number of available parking spaces. The client will then print out the return string from the server, exactly as sent from the server. Then, the client will exit.

If called with the "reserve" command-line argument, the client will ask the server to reserve a parking space. The client will then print out the return string from the server, exactly as sent from the server. Recall that a reserve request can fail with a specific kind of return string. Then, the client will exit.

Use any reasonable format for the message between client-and-server and between server-and-client. You may use any source code, with proper acknowledgement, from Jim Frost, Paul Lu, or our textbook.

The following elements are required of your programs (i.e., client program and server program):

1. Use the UNIX Socket API with TCP/IP-based sockets (i.e., AF_INET) such that the client and server can be on different computer systems.

2. As discussed in class, it is strongly, strongly preferred that you write your programs in the C language. Python and Java implementations are also acceptable. If you wish to use a different language, please contact the instructor first.

3. Write your programs for Linux or any Unix-like operating system. If you wish to use a different operating system, please contact the instructor first.

4. Provide instructions or a script for how to compile your program. A Unix-like Makefileis the preferred way.

5. Be sure to comment your code to make it more understandable. In particular, comment on the message formats used.

6. Submit all source code files (i.e., .c, .h, and Makefile) to your instructor.