nt92/bittorrent

Hey! I'm Nikhil. 👋🏽

📈 Github Stats

bittorrent's Issues

Optimize threads with closing connections

After a thread has run its course, we should be able to close it and drop the connection so that we are not wasting space/cpu. For example, we can do this when a transfer is completed and the file is on the peer, it will not need any more outward requests so we can remove its threads looking for pieces.

Crunch Time v1

• Choke/unchoke timer/logic (download rates etc.)
• New Logger architecture to handle multiple peers on the same machine (so we can actually test)
• Change Message architecture
• Create MessageDispatcher

Run remotely on CISE machines

File Chunker

Details

• Size: 20 megabytes
• Chunk size: 16384 bytes

Resources

• File to byte[]

Messages

Details

message length	message type	payload

• Message length: 4 byte field, specifies the message length in bytes
• Message type: Specifies the type of message. See below.
• Message payload: Variable size, varies by message type.

Message types

message type	value
choke	0
unchoke	1
interested	2
not interested	3
have	4
bitfield	5
request	6
piece	7

Message payloads

To do...

Handshake

Details

handshake header	zero bits	peer ID

• Handshake header: 18 byte string "P2PFILESHARINGPROJ"
• Zero bits: 10 byte zero bits
• Peer ID: 4 byte integer representation of the peer ID

Complete remaining message handlers

Some handler delegate methods are stubbed rn, we need to implement them.

HandshakeMessage Struct

Logging System

File Handler

for a peer,

• determine what file-pieces peer has
• determine if peer has all file-pieces
• save file-piece
• compile file-pieces into complete file

FileHandler

Add functionality to FileHandler so we can utilize its data to compare/send pieces of the actual file being transferred.

Create test environment for generating list of peers and connecting

Times for getPreferredPeers() and getOptimisticallyUnchokedPeer()

Create the functions that will run on the given intervals for recalculating peers