Basically you need a server (well, you don't NEED a server, but it would make it much simplier) that would store user IPs between other things like file hash lists, etc. That server can be in any enviroinment you want (which is very comfortable).
Then, each client connects to the server (it should have a dns, it can be a free one, I've used no-ip.com once) and sends basic information first (such as its IP, and a file hash list), then sends something every now and then (say each 5 minutes or less) to report that it's still reachable.
When a client searchs files/users, it just asks the server.
This is a centralized network, but the file sharing would be done in p2p client-to-client connections. The reason to do it like this is that you can't know an IP to connect to without some reference.
Just to clear this server thing up: - Torrents use trackers. - eMule's ED2K uses lugdunum servers. - eMule's "true p2p" Kademlia uses known nodes (clients) (most of the time taken from servers like this).
It's a fully decentralized BitTorrent Client from the Delft University of Technology. It's Open Source and written in Python, so also a great starting point to learn.
发布评论
评论（4）
基本上你需要一个服务器（好吧，你不需要服务器，但它会让事情变得更简单）来在文件哈希列表等其他东西之间存储用户IP。
该服务器可以在您想要的任何环境中（这非常舒适）。
然后，每个客户端连接到服务器（它应该有一个dns，它可以是免费的，我曾经使用过no-ip.com一次）并首先发送基本信息（例如它的IP和文件哈希列表） ，然后时不时地发送一些内容（比如每 5 分钟或更短时间）来报告它仍然可以访问。
当客户端搜索文件/用户时，它只是询问服务器。
这是一个集中式网络，但文件共享将在 p2p 客户端到客户端连接中完成。
这样做的原因是，如果没有一些参考，您就无法知道要连接的 IP。
只是为了清理这个服务器问题：
- 种子使用跟踪器。
- eMule 的 ED2K 使用 lugdunum 服务器。
- eMule 的“真正的 p2p”Kademlia 使用已知节点（客户端）（大部分时间取自服务器 像这样）。
Basically you need a server (well, you don't NEED a server, but it would make it much simplier) that would store user IPs between other things like file hash lists, etc.
That server can be in any enviroinment you want (which is very comfortable).
Then, each client connects to the server (it should have a dns, it can be a free one, I've used no-ip.com once) and sends basic information first (such as its IP, and a file hash list), then sends something every now and then (say each 5 minutes or less) to report that it's still reachable.
When a client searchs files/users, it just asks the server.
This is a centralized network, but the file sharing would be done in p2p client-to-client connections.
The reason to do it like this is that you can't know an IP to connect to without some reference.
Just to clear this server thing up:
- Torrents use trackers.
- eMule's ED2K uses lugdunum servers.
- eMule's "true p2p" Kademlia uses known nodes (clients) (most of the time taken from servers like this).
Tribler 就是您正在寻找的！
它是来自代尔夫特理工大学的完全去中心化的 BitTorrent 客户端。它是开源的，用 Python 编写，因此也是一个很好的学习起点。
Tribler is what you are looking for!
It's a fully decentralized BitTorrent Client from the Delft University of Technology. It's Open Source and written in Python, so also a great starting point to learn.
使用DC++
Use DC++
Bit-Torrent 有什么问题吗？
编辑：Microsoft 操作系统上还有一个预构建的 P2P 网络，作为构建某些东西的基础非常酷。 http://technet.microsoft.com/en-us/network/bb545868。 ASPX
What is wrong with Bit-Torrent?
Edit: There is also a pre-built P2P network on Microsoft operating systems that is pretty cool as the basis to build something. http://technet.microsoft.com/en-us/network/bb545868.aspx