Java program - Online Address Book (server client application)

Online Address Book II

1. The Assignment 2

For this assignment, the server must allow multiple clients connect the server at the same time. You are required to implement a multithreaded server (such as Pthread or Java thread) and a client that can monitor the server’s message and the user’s input at the same time (e.g. using select() or threads).

Besides the original five commands ADD, DELETE, LIST, SHUDOWN, QUIT, you will need to implement four new commands, LOGIN, LOGOUT, WHO, LOOK, on the client side and the corresponding functions on the server side.

The details of the protocol depend on the command the client sends to the server.

LOGIN

Identify the user to the remote server. A client that wants to login should begin by sending the ASCII string “LOGIN" followed by a space, followed by a UserID, followed by a space, followed by a Password, and followed by the newline character (i.e., '\n').

Your server should be initialized with the UserIDs and Passwords of at least four users who will be allowed to execute the ADD, DELETE, and SHUTDOWN (the root user only) commands at the server. However, a user is allowed to execute the LIST, WHO, LOOK, and QUIT commands anonymously (without login).

When the server receives a LOGIN command from a client, it should check if the UserID and Password are correct and match each other. If they are not correct or don’t match each other, the server should return the string “410 Wrong UserID or Password,” otherwise it should return the “200 OK” message.

A client-server interaction with the LOGIN command thus looks like:

c: LOGIN john john01

s: 200 OK

LOGOUT

Logout from the server. A user is not allowed to send ADD, DELETE, and SHUTDOWN commands after logout, but it can still send LIST, LOOK, WHO, and QUIT commands.

A client-server interaction with the LOGOUT command looks like:

c: LOGOUT

s: 200 OK

WHO

List all active users, including the UserID and the users IP addresses.

A client-server interaction with the WHO command thus looks like:

c: WHO

s: 200 OK

The list of the active users:

john 141.215.10.30

root 127.0.0.1

LOOK

Look up a name in the book. Display the complete name and phone number record. A client sends the ASCII string “LOOK" followed by a space, followed by a number (1 – look for the first name, 2 – look for the last name, 3 – look for the phone number), followed by a name or a phone number, and followed by the newline character (i.e., '\n').

When the server receives an LOOK command from a client, it will look up the name or the phone number in the address book. When there is a match, it returns the “200 OK” message and all the matched record (s). If there is no match, it returns the “404 Your search did not match any records”.

A client-server interaction with the LOOK command thus looks like:

c: LOOK 2 Miller

s: 200 OK

Found 2 match

1001 David Miller 313-510-6001

1004 John Miller 315-123-1345

c: LOOK 3 313-231-1324

s: 404 Your search did not match any records

ADD and DELETE

The basic requirement is the same as the assignment 1 except that a user needs to login first to execute these commands. If a user has not logged in, the server will return a "401 You are not currently logged in, login first" message

LIST

Same as the assignment 1.

SHUTDOWN

The basic requirement is the same as the assignment 1 except that only the “root” user can execute this command. When your server receives a SHUTDOWN command from a client, it should check if the current user is the root. If it is not the root user, the server should return a "402 User not allowed to execute this command" message.

In addition, the SHUTDOWN will make all clients and the server terminate.

A client-server interaction with the SHUTDOWN command thus looks like:

c: SHUTDOWN s: 200 OK

At the windows of all clients

s: 210 the server is about to shutdown ……

QUIT

If a user logged in from the current client, QUIT also logout the user.

Note, a user can execute WHO, LIST, and QUIT commands before logged in.

2. Format

You should form a team of two students (or work individually) and then jointly design your project. While each project should be an integrated effort, you should identify in your README file what part of the project each member is responsible for.

I assume you will work in the same group as you did for project 1. If there is any change, please let me know.

3. Programming Environment

You can use either C/C++ or Java to implement the assignments. The assignments will be tested on the UMD Login servers (login.umd.umich.edu). For easy grading, please don’t use any GUI interface.

4. Requirements

The following items are required for full-credit:

· implement all nine commands: ADD, DELETE, LIST, QUIT, SHUTDOWN, LOGIN, LOGOUT, WHO, LOOK

· all users share the same address book. The users information should be maintained by the server. You must have the following users (lower case) in your system:

UserID Password

root root01

john john01

david david01

mary mary01

· make sure that you do sufficient error handling such that a user can't crash your server. For instance, what will you do if a user provides invalid input?

· the client should be able to connect to the server running on any machine. Therefore, the server IP address should be a command line parameter for the client program.

· the server should print out all messages received from clients on the screen.

· when the previous client exits, the server should allow the next client connect.

· your source codes must be commented

· include a README file in your submission.

· include a Makefile in your submission.

Note: in your README file, the following information should be included: the functions that have been implemented, the instructions about how to compile and run your program, known bugs. Also, in either the README or a separate PDF or DOCX, you should have sample outputs of a complete test of all commands you implemented.

5. Grading (100 points)

· Correctness, Robustness, and Documentation of Working Program (90 points)

· You will lose at least 10 points for any bugs that cause the system crash.

· You will lose at least 5 points for any other bugs.

· You must turn in screen shots in a PDF or DOCX file of that program working – verifying the new functionality

· Comments and style (5 points)

· README (5 points)

1