<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://aspadvice.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Integrating P2P into Applications</title><link>http://aspadvice.com/forums/345/ShowForum.aspx</link><description>Integrating P2P technology into an application takes more than programming, it takes design and concept. Generally an application needs to be thought of differently when making P2P a core part of the value proposition. Come discuss how P2P affects the whole software development effort.</description><dc:language>en</dc:language><generator>CommunityServer 2.1 (Build: 60809.935)</generator><item><title>Recap</title><link>http://aspadvice.com/forums/thread/12876.aspx</link><pubDate>Sun, 25 Sep 2005 22:50:24 GMT</pubDate><guid isPermaLink="false">e709ad4c-0c15-48eb-915e-c462c6e85445:12876</guid><dc:creator>MichaelLatta</dc:creator><slash:comments>0</slash:comments><comments>http://aspadvice.com/forums/thread/12876.aspx</comments><wfw:commentRss>http://aspadvice.com/forums/commentrss.aspx?SectionID=345&amp;PostID=12876</wfw:commentRss><description>&lt;P&gt;The discussion was very good.&amp;nbsp; We started with what makes a P2P application different.&amp;nbsp; What components tend to be present in a P2P application that may be optional or limited in other cases.&amp;nbsp; Concensus was that all the key components were required for a P2P application to function.&lt;/P&gt;
&lt;P&gt;1) Some way to locate other peers.&lt;/P&gt;
&lt;P&gt;2) Som way to authenticate/trust other peers.&lt;/P&gt;
&lt;P&gt;3) Some way to know if other peers are available/online/etc.&lt;/P&gt;
&lt;P&gt;4) Some way to exchange information with the peers.&lt;/P&gt;
&lt;P&gt;There was a good discussion of various frameworks available for P2P applications.&amp;nbsp; The use of game related SDKs came up several times as worth evaluating.&amp;nbsp; The new WCF support for P2P applications looks quite promising with the PDC bits supporting PNRP.&lt;/P&gt;
&lt;P&gt;There was a long discussion&amp;nbsp;of what it takes to make P2P applications work in real networks where firewalls and NAT can cause connectivity problems.&amp;nbsp; Port 80 tunneling was seen as a requirement in many IT environments as even opening a small range of ports for P2P applications is hard to get past central IT departments.&amp;nbsp; The IPv6 based tunneling in the MS environment was seen as one of the more complete solutions, but may need to be configured/enabled in XP while it is expected to be enabled by default in Vista.&lt;/P&gt;
&lt;P&gt;Finally the last major point was that many found it easier and more secure to use a central server for peer resolution and authentication.&amp;nbsp; The need to verify peer identity without a central authority was a major issue for some present that are more in the mobility space.&amp;nbsp; In general verification of trust in a P2P application becomes harder without some central management.&amp;nbsp; The data trafic can be done P2P, but a client/server model for initiating conversations was seen as often desireable.&amp;nbsp; The 2 cases where this does not work is when the application must support interactions without access to the internet (in a secure setting, on the battlefield, or in a hotel room without an internet connection).&amp;nbsp; The biggest problem with true P2P applications is that they turn each machine into a server, with all the security/vulnerability issues that entails.&lt;/P&gt;</description></item></channel></rss>