Problem Definition

Implementation of a (lite) version of Chord Distributed hash table system. We have developed a P2P system for downloading RFCs. Every communication is done via messages that resemble HTTP-like message formats.

Team Members

1. Salil Kanitkar : [email protected]
2. Sagar Sane
3. Mayur Awagadhe
4. Sagar Natekar

Types of Messages

Chord Peer <-> Peer Messages

1. RegisterNode
2. NodeIdentity
3. FixFingers
4. GetDb
5. GetKey
6. NodeList
7. GetRFC
8. ForwardGet
9. GetFinger
10. PutKey
11. RemoveNode
12. ExitNow

Chord Peer <-> Client Messages ->

1. PrintRFCDb
2. PeerDetails
3. FetchRFC
4. PeerExit

Message Types and formats -->

1. FetchRFC GET FetchRFC Chord-LT/1.0 IP: Port:

2. RegisterNode GET RegisterNode Chord-LT/1.0 IP: Port:

3. NodeIdentity

   This message format may change. Do we need to add some more fields

   POST NodeIdentity Chord-LT/1.0 chord_id: successor_id: pred_id: successor_IP: successor_Port: pred_IP: pred_Port:

4. GetKey GET Getkey Chord-LT/1.0 IP: Port: Chord-Id:

5. NodeList POST NodeList Chord-LT/1.0 IP: Port: count:

   :: :: . . . . . ::

6. GetRFC GET GetRFC Chord-LT/1.0 IP: Port: RFC-Value: Flag:0

7. PrintRFCDb GET PrintRFCDb Chord-LT/1.0

8. ForwardGet GET ForwardGet Chord-LT/1.0 IP: Port: RFC-Value:

9. PeerDetails GET PeerDetails Chord-LT/1.0 IP: Port: