Introduction

In this assignment you are tasked with creating a Java application designed to handle the management and download of video game data, similar to Steam. Steam is an online platform that distributes video games in a digital format.

• The application you will develop is simpler in design. It doesn't need to have many of the features available in Steam, such as the ability to purchase or trade video games.

The app consists of separate Server and Client components, connected to each other using socket programming. The Server component maintains a database to store information, and the Client side of the app allows clients to request information and files from the server.

Objectives

• Review the concepts of socket programming and database management.
• Create a local Server to store information about video games and user accounts.
• Allow clients to create accounts, log in, and log out.
• Use a hashing algorithm to implement secure password storage.
• Enable clients to download video game files (represented by PNG files for simplicity) from the Server.
• Write a detailed report on the assignment.

Tasks

Ensure to Fork this repository and clone the fork to your local machine. Create a new Git branch before starting your work.

1. Design the application's Client-Server API

The Client and Server sides of the app should be able to communicate with each other in a predetermined manner. In order to achieve this, a series of Request-Response interactions between the Client and the Server can be implemented.

1.1. Request

A Request must have these features:

• A Request is sent from the Client to the Server over the network.
• You should create different types of Requests for different actions.
• A Client can Request a list of available games, info about a specific game, or to download a game. Creating an account, logging in, and logging out can also be considered Requests.
• It is up to you to design the Request's format. For example, A Request can be a JSON string which is easy to send on a socket.

1.2. Response

A Response must have these features:

• A Response is sent from the Server to the Client over the network.
• You should create different Response types corresponding to the received Request.
• Attach appropriate data to the Response based on the Request. A Response might contain the data a user has requested, or it might just be a boolean indicating the result of a previously sent Request (such as confirming a user's login attempt by returning a True boolean).
• It is up to you to design the Response's format. Similar to a Request, a Response can also be a JSON string.

Note that each Request received from the Client must be answered with a Response from the Server. Include details about how you designed the Request-Response interactions in your report.

2. Design the application's architecture

The Client and Server are the two main components of your app. They must be connected through the use of a socket connection.
Plan out your project's files accordingly. Any file designed for the Client side must be stored in the Client package and any file designed for the Server side must be stored in the Server package. Classes that can be used by both sides should be stored in the Shared package.

2.1. Client

The Client component must provide a graphical or command-line interface for users to interact with the app. It should allow users to:

• Create accounts by providing a username, a password, and a date of birth (DOB)
• Log in and log out securely (more info in section 5)
• Browse the available video game catalog
• View each individual game's details
• Download video game files and manage these downloads

The Client must provide the following functionalities:

• Socket Connection: Establish a connection with the Server over the local network using socket programming.
• Request Generator: Generate Requests based on the user's input.
• Response Handler: After sending a Request, wait to receive a Response from the Server. Then provide the user with appropriate info based on the response type.
• Download Manager: If a user requests to download a game, the Download Manager ensures the file is downloaded successfully and stores it in the correct format in a specified directory.

2.2. Server

The Server component is responsible for handling Client requests, managing the database, and sending video game files to the Client. Before a Server is ready to accept clients, it must connect to the database to access the stored information:

• At the start of the first run of your Server, it must read data from the files located in the Resources folder and import it to the database. This process is explained in more detail in section 4.
• Your program must run a query on the database according to the received Request.
• Every time a new account is created, the account credentials must be added to the database.
• If a user requests to download a video game, you must update the number of times that the game has been downloaded by that user.

The Server must provide the following functionalities:

• Socket Listener: Listen for incoming Client connections and redirect requests to the appropriate handlers. Once a request has been fully handled, enter listening mode again.
• Request Handlers: Process Client Requests and interact with the database to fetch the requested data. You may need to create multiple handlers for various Requests.
• Database Manager: Interact with the database system to perform CRUD (Create, Read, Update, Delete) operations. (more info in section 3)
• Response Generator: The final step in handling a Request is to send an appropriate Response to the Client. Attach the needed data to the Response based on the Request.
• Logging: Try to log every major action the Server performs (e.g. accepting a Client, sending a file, etc.) to simplify the debugging process.

3. Create a Database to store the app's data persistently

The Server's database plays a central role in storing essential data. You are allowed to use a SQL-based database or a NoSQL database (such as MongoDB). Remember to add the necessary JDBC (Java Database Connectivity) dependency to your project.
The database must contain the following data:

3.1. Games

This table stores information about video games, including their attributes.

Column name	Data type	Description
id	text	A unique identifier for the game
title	text	Title of the video game
developer	text	Name of the studio that developed the game
genre	text	Genre of the video game
price	double precision	Current price of the video game
release_year	integer	The game's release year
controller_support	boolean	This parameter is True if the game supports controllers
reviews	integer	A value from 0 to 100 indicating the game's average user score on Steam (higher is better)
size	integer	Size of the game in kilobytes
file_path	text	Path of the game file stored in the Resources folder

3.2. Accounts

This table stores information about user accounts.

Column name	Data type	Description
id	text	A unique identifier for the account
username	text	Username of the account
password	text	Hashed password of the account
date_of_birth	date	The user's date of birth

3.3. Downloads

This table stores information about user downloads.

Column name	Data type	Description
account_id	text	A unique identifier for an existing account
game_id	text	A unique identifier for an existing game
download_count	Integer	The number of times a user has downloaded a specific game

- Note that you are allowed to change the structure and number of tables, but you are required to store all the mentioned attributes.

Regardless of how you implement the database, it must be able to answer questions such as:

• How many accounts have been created?
• What is the average price of the available video games?
• How many times in total has a game been downloaded?
• How many DISTINCT users have downloaded a game?

4. Import the necessary data from the Resources folder

• Alongside the Server component, a Resources folder is provided that stores 10 TXT files (each storing a game's attributes) and 10 PNG files (each representing a game's data). The TXT files and the PNG files are paired together based on their names (which is always the game id).

• Before the Server starts accepting requests from clients, it must first import all the game data from TXT files and store them in the database. This is a one-time-only process, once the data has been successfully imported to the database, the Server doesn't need to import the data on subsequent runs.

• Ensure to store each PNG file's path in the file_path column of the Games table. Whenever a user requests to download a specific video game, the Server must send the respective PNG file to the Client. The Client then stores that file in the Downloads folder

• Each TXT file is structured like this:

  • gameid
  • title
  • developer
  • genre
  • price
  • release_year
  • controller_support
  • reviews
  • size

  
  Here's an example of a TXT file:

  2050650
  Resident Evil 4
  Capcom
  Survival Horror
  59.99
  2023
  True
  97
  618

5. Use a hashing algorithm to provide security for accounts

• To ensure the security of user accounts, the app should implement password hashing. When a user creates an account or changes their password, apply a hashing algorithm (e.g. bcrypt) to transform the password into a secure, irreversible form. The hashed passwords must then be stored in the database. DO NOT store the plain password in the database.
• Note that when an existing user tries to log in, the password they provide must be hashed again and compared to the hashed password that is stored in the database. Login is successful only if the two hashed values are equal.
• You can add the JBCrypt package to your dependencies and use the hash functions provided in the package.

6. Provide a backup of the database you created

• There are multiple ways to back up your database based on the DBMS you're using.
• If you're using PostgreSQL for example, you can open pgAdmin, right-click on your database, and choose the Backup option to save a copy of your database.
• Place the backup file in the project's Database Backup folder.

7. Commit your changes and push your commits to your fork on GitHub. Create a pull request (assigned to your mentor) to merge your changes to the main branch of your fork on GitHub.

Notes

• You are allowed to modify or delete all the provided code. Add as many classes and tables as you need. Do not limit yourself to the existing classes and methods.
• You are NOT allowed to change the contents of the Resources folder located on the Server side.
• Note that the Client side of the program cannot access the database directly and must connect to the Server to ask for data.
• If you decide to use JSON strings in your program, you may find the gson package to be useful for serializing a Java object to JSON.
• Your report should include details on the architecture you used for the app, as well as the design process of your database. Provide adequate explanation regarding each component of the app. Specify the primary key chosen for each table and how you ensured it would be unique.

Bonus Objectives

1. Add a GUI (Graphical User Interface) to your project. It's recommended to use JavaFX. This GUI should include all the options offered by the command line menu you implemented earlier. Once a download is complete, display the PNG picture received from the database in the GUI.
2. Use multithreading in the Server side code to allow multiple clients to connect concurrently. This can be done by creating a main listener thread that waits for connections from clients. Once a Client has connected, create a new thread to handle that specific Client.
3. Use multithreading to speed up the download process by creating multiple data streams that run in parallel to each other.
4. Implement an age restriction system for video games. Prevent users who are younger than a specified age to access certain games. You can add a new age restriction column to the Games table.

Evaluation

• Your code should compile and run without any errors
• Your code should be well-organized, readable, properly commented, and should follow clean code principles
• Your Database should be well-structured with as little data redundancy as possible
• You should use Git for version control and include meaningful commit messages

Submission

• Push your code to your fork on GitHub
• Upload a backup of your database to your fork on GitHub
• Upload your report to your fork on GitHub

The deadline for submitting your code is Wednesday, May 31 (10th of Khordad). Good luck and happy coding!