Index for bindings in this series:
The last standard binding in the series is the NetPeerTcp binding for the PeerChannel transport. The peer transport is a multiparty network transport that sends messages across a mesh of peers. The NetPeerTcp binding requires installing the Peer-to-Peer networking service in Windows. Without this service installed, you cannot create an instance of the binding because it attempts to contact the peer name resolver.
Although the NetPeerTcp binding supports the same security settings, None, Transport, Message, and TransportWithMessageCredential, as the NetTcp binding, I'm going to break the usual pattern by not going over the modes individually. As far as I can tell, changing the security mode doesn't actually rely on changing the channel stack of the peer transport for configuration.
MaxReadPoolSize: 64MaxSessionSize: 2048MaxWritePoolSize: 16ReaderQuotas: MaxArrayLength: 16384 MaxBytesPerRead: 4096 MaxDepth: 32 MaxNameTableCharCount: 16384 MaxStringContentLength: 8192
ListenIPAddress: ManualAddressing: FalseMaxBufferPoolSize: 524288MaxReceivedMessageSize: 65536Port: 0Scheme: net.p2p
The two parts of this binding are the transport element and the peer resolver element. The peer resolver is the portion that translates an ID for the peer mesh to a collection of endpoint addresses in the mesh. The remaining configuration settings on the binding are two related to the peer resolver and the standard ones common to all bindings.
CloseTimeout: 00:01:00EnvelopeVersion: Soap12 (http://www.w3.org/2003/05/soap-envelope)IsPnrpAvailable: TrueNamespace: http://tempuri.org/OpenTimeout: 00:01:00ReceiveTimeout: 00:10:00Resolver: System.ServiceModel.PeerResolvers.PeerResolverSettingsSendTimeout: 00:01:00
Next time: How Block Ciphers Work