In this project, we will develop a simplified version of peer-to-peer file distribution system. The goal of the project is to develop a Napster-like filesharing system.
You may work in groups of two. The groups should be reported by Wednesday, Mar 23rd.
To keep the user interface simple, you should build two simple programs one for server and one for the peers.
The server program is responsible for (1) building and maintaining a list of active peers in the network, (2) building a database of files each peer is sharing, and (3) respond to search queries from peers.
The peer code should be started with the number for the peer's own control port, the name and port number of a central server, and a list of files to share. The peer will accept file requests from other peers through the control port and respond to them.
We will only exchange ASCII files in the system.
All server communication should use UDP as transport layer protocol whereas file transfer between the peers should use TCP.
Following are the application level messages sent from/to the server using UDP sockets:
REGISTER peer-IP peer-port num-files file1 file2 file3 ... fileN
This command registers a peer with the server where
peer-port are the IP address and port number through which it will handle file requests (sent from peer to server).
The command is used to register newly downloaded files as well (without including the ones registered earlier).
REGISTERED peer-IP peer-port num-files
This command acknowledges that the peer is successfully registered with the server (sent from server to peer).
If the client does not get a REGISTERED reply to a REGISTER message after a minute than it should assume the registration has failed and record the event in
error.log without retrying to register.
KEEPALIVE peer-IP peer-port
Used as a heartbeat every one minute, this command indicates that the peer is alive (sent from peer to server). If the heartbeat message is not received from a node for more than a minute it is removed from the system.
This command asks for location of a file (sent from peer to server).
LOCATION file-name peer-IP peer-port
This command indicates the location of a file in response to a QUERY message (sent from server to peer).
Note that, there is no space after each message.
Following are the application level messages sent between peer using TCP sockets:
This command asks for indicated file.
REPLY file-name file-size file-content
This command sends the requested file along with file size of the file being sent.
Note that, each file request is handled by a seperate active socket. This socket should be terminated when the file transmission is completed.
Report all major actions as the program communicates with other server/peers.
We assume file size to be at most 16K characters.
We assume a client to share at most 255 files.
We assume file names to be at most 64 characters without any white space characters.
When a malformed message is received report it in a log file named
If you are developing advanced features such as load balancing by dividing files into chunks, develop two versions of code. One with the required functionality and nothing more and another one with advanced features that you added.
You must submit all the source code with sufficient comments to help understand the code.
You must include in your submission a file named
includes your name and a brief description of your submission, including the name
of each file submitted along with a one line description of what is in the file.
If your code is not complete, tell us what works and what doesn't. If you are submitting code that does not compile, please tell us that as well. If you borrow code from someone else, you are required to tell us about it (this must also be documented in the code itself).
Finally, feel free to include a description of any problems you had or anything else you think might be helpful to us.
Your project will be tested to make sure it works properly. We will test your clients and servers against each other. That is, your server should be able to exchange files with clients developed by someone else.
Your grade will depend on the functionality and the code quality. Hence, please pay careful attention to clean, modular and extensible design as you implement the project. This is also an opportunity to experiment with rapid prototyping languages such as Python, Ruby, and others.
There will be bonus grades for extra functionality not required by the project (optional and at the discretion of the instructor).
Submission of your project is via WebCT. You must submit all the required files in a single tar or zip file containing all the files for your submission.