Geek Answers Handbook

Any problems with the System.Net.PeerToPeer library?

I studied the namespace for System.Net.PeerToPeer in .NET 4.0, and the classes presented in this library seem good enough to build P2P networks. However, when I look for examples and links, I can only find old obsolete examples or links that simply point to the MSDN documentation. It seems that not too many people use this library and that there is not much effort in this product. Does anyone know of problems with this library that I don’t know about, can convince me not to use it? I saw that older versions of windows do not support it, but this is not a show stopper for me. Is there anything else?

+5
source share
2 answers

This API is based on PNRP . This requires an IPv6 connection (at least via Teredo); this is usually not available in modern installations and requires administrative effort to configure it. I think this is the main reason why there is so little interest.

0
source

I must disagree with the previous answer.

While the P2P mechanisms built into .NET use PNRP, limited online examples have more to do with developer ignorance than any network restrictions.

I developed a rather complex P2P application using the peer channel / netPeerTcpBinding. This application works almost without problems in Windows XP SP3 or higher and works through the Internet.

IPv6 XP SP3 +, , PNRP. , , , 95% .

, , . Teredo, UDP 3544. 2 PNRP (XP SP3 +) NAT.

, P2P - .

+9

More articles:


All Articles