none
Why PeerChannel (NetPeerTcpBinding) Is Deprecated? RRS feed

  • Question

  • Hi,

    I am making a system based on gossip, I thought of using WCF P2P, .NET 4.5 marked PeerChannel (NetPeerTcpBinding) as deprecated.

    1- Why is it deprecated? 

    2- Will there be an alternative? 

    I hope WCF team guys answer here. it is quite strange to deprecate such a feature that most frameworks don't have. it was quite unique! 


    Alan-SY


    • Edited by Alan-Sy Sunday, November 23, 2014 6:30 AM
    Sunday, November 23, 2014 6:28 AM

All replies

  • Hi,

    For this scenario, NetPeerTcpBinding still exists and is supported in.NET Framework 4.5. It is deprecated, meaning, it could potentially be removed in future versions.

    Unfortunately, there is no direct replacement suggested for NetPeerTcpBinding via Product Group.

    For new development efforts, it is strongly recommended to look at other ways to accomplish the same functionality. This would depend on what functionality/problem NetPeerTcpBinding is intended to solve in the application. While there isn’t a direct binding replacement to NetPeerTcpBinding, most of the features can be accomplished using other bindings or combination of bindings.

    For more information, you could refer to:

    https://social.msdn.microsoft.com/Forums/en-US/d57057f5-c670-4e78-9d26-cf85898ac2bd/netpeertcpbinding-marked-obsolete-in-net-45?forum=wcf

    https://social.msdn.microsoft.com/Forums/en-US/889e399c-c0c6-4a45-b7dd-5102b2230cba/netpeertcpbinding-obsolete-why-any-replacements-?forum=wcf

    Regards

    Monday, November 24, 2014 2:45 AM
    Moderator
  • Hi Shawn, Thank you so much for the quick reply.

    I understand it is still supported with .Net 4.5, but it is new development and we may upgrade to the next .Net version when it is available. Implementing PeerChannel protocol is not easy task, it requires a lot of work to implement the meshed tree. I am not talking about peers resolving, I am talking about messaging exchange and redundancy control, reconstructing the mesh after faults, implementing heartbeats, hop counts, ... etc.

    I hope we know the answer of "Why" it is deprecated, "Because .. "? deprecating a feature without explanation or suggestions is not a nice behavior from a big company we love. 


    Alan-SY

    Monday, November 24, 2014 3:02 AM
  • Hi Alan-Sy:

    I am also wondering about this situation but can not find the detailed explanation, here is what I find:

    http://w3facility.org/question/alternative-to-netpeertcpbinding-in-wcf/

    Tuesday, November 25, 2014 2:36 AM