WCF-NetNamedPipe Transport Properties Dialog Box, Receive, Binding Tab
Use the Binding tab to define the binding properties specific to the WCF-NetNamedPipe receive adapter. The WCF-NetNamedPipe adapter provides efficient cross-process communication in a .NET-to-.NET environment. The adapter uses the named pipe transport and messages have a binary encoding. This adapter cannot be used in cross-computer communication.
Note
The current version of the WCF-NetNamedPipe adapter does not support WS-Reliable Messaging.
| Use this | To do this |
|---|---|
| Open timeout (hh:mmss) | Specify a time span value that indicates the interval of time provided for a channel open operation to complete. This value should be greater than or equal to System.TimeSpan.Zero. Default value: 00:01:00 Maximum value: 23:59:59 |
| Send timeout (hh:mmss) | Specify a time span value that indicates the interval of time provided for a send operation to complete. This value should be greater than or equal to System.TimeSpan.Zero. If you use a request-response receive port, this value specifies a time span for the whole interaction to complete, even if the client returns a large message. Default value: 00:01:00 Maximum value: 23:59:59 |
| Close timeout (hh:mmss) | Specify a time span value that indicates the interval of time provided for a channel close operation to complete. This value should be greater than or equal to System.TimeSpan.Zero. Default value: 00:01:00 Maximum value: 23:59:59 |
| Maximum received message size (bytes) | Specify the maximum size, in bytes, for a message including headers, which can be received on the wire. The size of the messages is bounded by the amount of memory allocated for each message. You can use this property to limit exposure to denial of service (DoS) attacks. Default value: 65536 Maximum value: 2147483647 |
| Enable transactions | Specify whether a message is submitted to the MessageBox database using the transaction flowed from clients. If this property is set, the clients are required to submit messages using the transaction protocol specified in the Transaction protocol property. If the clients submit messages outside the transactional scope then this receive location returns an exception back to the clients, and no messages are suspended. The option is available only for one-way receive locations. If the clients submit messages in a transactional context for request-response receive locations, then an exception is returned back to the clients and no messages are suspended. The default value is cleared. |
| Transaction protocol | Specify the transaction protocol to be used with this binding. Valid values include the following: - OleTransaction - WS-AtomicTransaction The default is OleTransaction. |
| Maximum concurrent calls | Specify the number of concurrent calls to a single service instance. Calls in excess of the limit are queued. Setting this value to 0 is equivalent to setting it to Int32.MaxValue. Default value: 200 |
Transaction Semantics on Message Failures
The following table describes the semantics of transactional message submission on message failures during inbound processing:
| Message submission result | Is the message suspended on failure? | Vote on the transaction outcome | Return result |
|---|---|---|---|
| Failure | Yes | Commit | Error |
| Failure | No | Abort | Error |
| Success | Yes | Commit | Success |
| Success | No | Commit | Success |
See Also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for