|
<netNamedPipeBinding> element
Defines a binding that is secure, reliable, optimized for on-machine cross process communication. By default, it generates a runtime communication stack with WS-ReliableMessaging for reliability, transport security for transfer security, named pipes for message delivery, and binary message encoding.
The netNamedPipeBinding element itself does not expose any configurable setting or attribute, but it should be used as grouping element for binding element(s) which each hold configuration settings for a particular binding.
| XML |
Copy Code
|
|---|---|
<netNamedPipeBinding> <binding closeTimeout="TimeSpan" hostNameComparisonMode="StrongWildCard/Exact/WeakWildcard" maxBufferPoolSize="Integer" maxBufferSize="Integer" maxConnections="Integer" maxReceivedMessageSize="Integer" name="string" openTimeout="TimeSpan" receiveTimeout="TimeSpan" sendTimeout="TimeSpan" transactionFlow="Boolean" transactionProtocol="OleTransactions/WS-AtomicTransactionOctober2004" transferMode="Buffered/Streamed/StreamedRequest/StreamedResponse"> <security mode="None/Transport"> <transport clientCredentialType="None/Windows" protectionLevel="None/Sign/EncryptAndSign" /> </security> <readerQuotas maxDepth="integer" maxStringContentLength="integer" maxByteArrayContentLength="integer" maxBytesPerRead="integer" maxNameTableCharCount="integer" /> </binding> </netNamedPipeBinding> |
|
Within the recommended default configuration, Smartsite iXperion uses a netNamedPipeBinding for both the StateSyncService and the InteropService, since both services only require local access. And a Named Pipe (at least within the WCF philosophy) provides just that: communication between different WCF applications on a single computer without giving access for communication from another machine.