p2p

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. I am looking for a reliable P2P framework or library, preferrably natively written in C#, but can also work with something C# can interface with. Have you came across or have worked with a solid one? Leniel Maccaferri Take a look at this link: Brunet: a

In the course of the last weeks, Android's NSD implementation is making me go mad: From a user's point of view, the following problems arise: Devices discover each other in a completely non-deterministic fashion. If I launch my NsdManager -based app, it works more or less if only two devices are involved. If a third device joins, it will seldomly discover the first two , and the first two will not see the third. If I exit the apps (they gracefully unregister the NSD listeners) and restart them in a different order, the discovery pattern is not exactly the same, but similar. In my home network,

Given a single public IP address (peer A) and a list of many other public IP addresses (a mix of IPv4 and IPv6 addresses), what is the easiest way to match up peer A the IP addresses of the n nearest peers without having the peers manually ping each other for latency benchmarking? I think that this is possible using BGP with a bunch of complicated queries (and maybe something involving OSPF), but I was hoping that there might be a solution or library that would make it as easy as the theoretical functional call below. // `peer` is a single IP address. `peer_list` is a list of IP addresses //

Is there any possible way to have browsers communicating to each other over lan/wan without the use of a server (direct peer-to-peer)? Looks like there may be hope on the horizon: http://www.w3.org/TR/webrtc/ IIRC, Opera released some kind of addition to their browser that embedded a webserver for just that functionality: http://unite.opera.com/ Not sure it really went anywhere, but I think its time will come. In pure HTML/Javascript? Probably not. To my knowledge, there's no good way in native JavaScript to listen for connections. In HTTP, the client opens a port, sends a request, and

今天看到一个问题，如何把一个文件快速下发到100w个服务器 如果我们将文件集中式地放在一个服务器或缓存上的话，带宽、连接都会遇到问题。 树状： 索引状： 无论哪种方法，好像速度都不够快，主要受制于资源和带宽。 P2P还是英文Point to Point （点对点）的简称。它是下载术语，意思是在你自己下载的同时，自己的电脑还要继续做主机上传，这种下载方式，人越多速度越快但缺点是对硬盘损伤比较大（在写的同时还要读），还有对内存占用较多，影响整机速度。 P2P的特点：1）无中央服务器，打破了C/S模式；2）用户之间互联并分享文件。 常见的P2P的协议有BitTorrent，这和我们天津大学的PT是一样的协议。 1、BT的简介 BitTorrent(简称BT)是一个文件分发协议，每个下载者在下载的同时不断向其他下载者上传已下载的数据。 而在FTP,HTTP协议中，每个下载者在下载自己所需文件的同时，各个下载者之间没有交互。 当非常多的用户同时访问和下载服务器上的文件时，由于FTP服务器处理能力和带宽的限制，下载速度会急剧下降，有的用户可能访问不了服务器。BT协议与FTP协议不同，特点是下载的人越多，下载速度越快，原因在于每个下载者将已下载的数据提供给其他下载者下载，充分利用了用户的上载带宽。通过一定的策略保证上传速度越快，下载速度也越快。 2、BT的原理解析