Peer-to-Peer File sharing system

A console based Peer to Peer (P2P) file sharing system with a centralized index (CI). Peers can join the system and share files (RFC text files) directly with each other. The centralized server is responsible for keeping a track what files each Peer and files it has.

Instructions to run the project:

The code has been tested on Windows 10 with Java 8 environment.

Run the Server by following below steps:

  cd src 
  javac com/p2p/server/Server.java 
  java com/p2p/server/Server

Once the server is up and running, run the Peer systems (can be more than one) by following below steps:

  cd src 
  javac com/p2p/client/Peer.java 
  java com/p2p/client/Peer <Server IP Address> 7734

Ignore the warnings that may come during the compilation step.

Notes:

When you run the Server, you will get system details in below format:

Initializing Server...
Server up at 192.168.0.14, Port = 7734
Version = P2P-CI/1.0, OS = Windows 10

Use the IP address (Here, 192.168.0.14) to start the Peer.

When a Peer joins the system:
Peer end:

Starting peer on Port Number = 8033, Host Address =  192.168.0.14
Client started at hostName = 192.168.0.14 ,port = 59792
Select from: ADD, LOOKUP, LIST, GET, QUIT

The first port number (Here 8033, is the Server maintained at Peer end's port number). The second port number (Here, 59792 is the port number through which it is connected with Centralized Server).

Server end:

Peer has joined with system with Hostname = 192.168.0.14, Port = 59792

This project does not allow spaces to be entered in the Title of the RFC.
Peer can choose from one of the following option:

ADD: This adds the rfc file details to the List maintained by the Server. Simply type "ADD" and Enter. Post that, Type the name of the RFC (i.e. number of RFC, for example 4) it has in the src/resources/localRFCs folder. If the RFC is present in that folder (RFC name should be like rfc4.txt, 4 represents the number you had put earlier), then Server will add the details. If the RFC is not present at Peer end, then 400 Bad Request will be raised and printed on console.
Peer end:

Select from: ADD, LOOKUP, LIST, GET, QUIT
ADD
Enter the RFC Name and RFC Title to be added (separated by space)
1 Host_Software
RFCDetails added successfully

Server end:

Server is processing below request:
ADD RFC 1 P2P-CI/1.0
Host: 192.168.0.14
Port: 10726
Title: Host_Software

RFCDetails added successfully

If the file that Peer is trying to add is not available in src/resources/localRFCs folder, below error is displayed at Peer end:

Select from: ADD, LOOKUP, LIST, GET, QUIT
ADD
Enter the RFC Name and RFC Title to be added (separated by space)
10 Unknown_File_Title
src\resources\localRFCs\rfc10.txt does not exists. Cannot add RFC details to Server.
Error: 404 Not Found

LIST: This will list all the RFC details and the peer details which has those files. (This list is maintained by Centralized Server).
Peer end:

Select from: ADD, LOOKUP, LIST, GET, QUIT
LIST
P2P-CI/1.0 200 OK
1 Host_Software 192.168.0.14 10726
2 test 192.168.0.14 10726

Server end:

Server is processing below request:
LIST ALL RFC P2P-CI/1.0
Host: 192.168.0.14
Port: 8033

LOOKUP: If a Peer wants to look up a particular RFC it is interested in, then it can give the name of the RFC (i.e. the number, for example 4). A list will be returned by the server which contains details of all the Peers which has this file and have ADDed its details into the system.
Peer end:

Select from: ADD, LOOKUP, LIST, GET, QUIT
LOOKUP
Enter the RFC Name and RFC Title to be looked up (separated by space)
1 Host_Software
P2P-CI/1.0 200 OK
RFC 1 Host_Software 192.168.0.14 10726
RFC 1 Host_Software 192.168.0.14 12460

Server end:

Server is processing below request:
LOOKUP RFC 1 P2P-CI/1.0
Host: 192.168.0.14
Port: 8033
Title: Host_Software

GET: If a Peer wants to GET a RFC from other Peers, it can simply raise a GET request and give the hostname and port number of the Peer it want to get the RFC from. Note that, these details can be obtained from the Lookup operation.
Peer Server end:

GET RFC 3 P2P-CI/1.0
Host: 192.168.0.14
OS: Windows 10

Peer Client end:

Select from: ADD, LOOKUP, LIST, GET, QUIT
GET
Enter the RFC Name to be downloaded and Hostname and Port number of the host where this RFC is present (separated by space)
1 192.168.0.14 12460
P2P-CI/1.0 200 OK
Date: Sun, 08 Nov 2020 21:45:45 GMT
OS: Windows 10
Last Modified: Sat, 31 Oct 2020 19:44:56
Content-Length: 21088
Content-Type: text/text

RFC has been downloaded. Date =  Sun, 08 Nov 2020 21, peerOS =  Windows 10, lastModified =  Sat, 31 Oct 2020 19, contentLength =  21088, contentType =  text/text

QUIT: A peer can Quit the system. When, it quits, the Server will remove all the RFC details from the List maintained by it.
Server end:

Connection is reset for client 192.168.0.14 port = 59811, removing it.

Peer end:

Select from: ADD, LOOKUP, LIST, GET, QUIT
QUIT
Quitting.

AmitMandliya/peer-to-peer

Peer-to-Peer File sharing system

Instructions to run the project: