Home
Knowledge Base
Credits
Site Map
 


Centralized Directory


Napster was the best known example of this type of P2P application

In this design, the P2P file-sharing service uses a large server (or server farm) to provide the directory service

The P2P application contacts the directory service, informing the directory service of its IP address and the names of objects in its local disk that it is making available for sharing

When an active peer obtains a new object or removes one, it informs the directory server, which then updates its database

Another way the directory server updates is by periodically sending messages to see which peers are still active, and when it determines that a peer is no longer connected, it removes the peer's IP address from the database



 

The directory server
collects this information
from each peer that
becomes active, thereby creating a centralized,
dynamic database

 

Drawbacks to the centralized directory

  • Single point of failure
    • If the directory server crashes, the entire P2P application crashes
  • Performance bottleneck
    • In a large P2P system, the centralized server must maintain a huge database
      and may have to respond to thousands of queries per second
  • Copyright infringement
    • It is easier for the legal system to shut down a centralized directory server