For this project, you're going to create a client-server connection using Java code that we've practiced in the Activities this semester.

This program is a very simple server-based program that has many uses in the modern age, such as online banking, online gaming, school registries, and many more.

For this project, we're going to create an application for online shopping.

The idea here is simple. A user should be able to browse a small selection of fruits from an online vender, choose which one(s) to purchase and how many, and end the transaction.

This is how it's going to work. A user will log on to the online store (which we will assume is done prior to the start of the application). For the purposes of this assignment, we're going to use ‘localhost' for the IP. You may use any PORT number you wish as long as it's not reserved.

When the application starts running, the user is logged in and given a list of fruits. The user may then select any of these options:

Display items chosen to buy

Purchase Bananas ($2 each)

Purchase Oranges ($3 each)

Purchase Pineapples ($5 each)

Purchase Watermelons ($8 each)

Finish Shopping

For the purposes of this assignment, we're going to assume that the user has an unlimited amount of money for shopping purposes. The store, however, does not. When the server connects, the client will get the inventory from the store's server so that the user will know how many of each item is in stock.

When the user selects to purchase an item, the user will be prompted for the quantity to buy. Upon giving a quantity, the user's cart should be updated with the number of the specific fruit and the client's inventory should decrease by the amount purchased. Finally, when the user decides to finish shopping, the program should display the total cost of the items the user purchased and close the connection.

When your program starts, the server should accept a connection from the client, and then generate a random inventory of items. Each item should have a random stock assigned from 10 to 20. The inventory values should be sent to the client, which will then display them to the user within the menu of purchase options. When a purchase is made, the inventory should be updated in the client for the item purchased.

The user's current list of items should be stored on the client end and displayed neatly when the user chooses to see it. Finally, when the user is done shopping, the final list of items should be sent to the server, which will calculate the total price and update its own inventory, then send the total price to the client which will display the total and then finish execution.

There are a few guidelines that you must follow for this program. When you have finished creating the program, make sure to check back over these guidelines to make sure that everything has been accounted for.

The guidelines are as follows:

The program must be a console-based application. No GUIs allowed.

The program must loop through the options until the user selects to exit.

You may get user input any way you choose - however, you must catch invalid entries. This means that if your options are 1-6, then a user entry ‘F' should be caught and give an invalid entry feedback, then allow the user to reenter their choice. Valid entries must also be checked when asking for quantities - positive integers only.

Your program must account for the amount of inventory in the store. If a user chooses to buy 10 pineapples and the store only has 8, then an error message should show and the purchase should not be completed.

User-friendliness is important! Make sure that your program looks nice and easy to use.

Send regular messages to the server's console. At the very least, send a message when the server connects, when input is received from the client, and when the server disconnects.

Make sure that in the natural runtime of your program when the server is disconnected that all sockets, scanners, and any other form of I/O is closed - leaving these open can cause a security leak that, while harmless on a localhost, can be dangerous on other IPs.