Which binding object should you use?

You create an application by using Microsoft Visual Studio .NET 2008 and the .NET Framework 3.5. The application exposes a Windows Communication Foundation (WCF) service that will be consumed by an ASP.NET application. The WCF application and the ASP.NET application will be

deployed on the same server. You need to ensure that the WCF service meets the following requirements:

The communication between the applications incurs minimum latency.
The binding satisfies the ordered delivery constraint that is specified in the service implementation by using the DeliveryRequirements attribute.

Which binding object should you use?

You create an application by using Microsoft Visual Studio .NET 2008 and the .NET Framework 3.5. The application exposes a Windows Communication Foundation (WCF) service that will be consumed by an ASP.NET application. The WCF application and the ASP.NET application will be

deployed on the same server. You need to ensure that the WCF service meets the following requirements:

The communication between the applications incurs minimum latency.
The binding satisfies the ordered delivery constraint that is specified in the service implementation by using the DeliveryRequirements attribute.

Which binding object should you use?

A.
NetTcpBinding

B.
WSHttpBinding

C.
NetPeerTcpBinding

D.
NetNamedPipeBinding

Explanation:
The WSHttpBinding and the NetTcpBinding are WS-* aware bindings that flow request messages (and possibly replies) from a sender to a recipient. Both bindings allow reliable messaging to be enabled by setting the ReliableSession.Enabled configuration property to true.

Sessions are implicitly supported by the connection-oriented NetTcpBinding’s underlying transport and independent of this setting, while enabling reliable sessions is required for session support with the WSHttpBinding.

The NetNamedPipeBinding sits on top of the Windows operating system’s support for reliable message delivery and reliable streams through named pipes. Because named pipes are connection-oriented, readily support sessions, are reliable by design, and are typically not bridged, there is no need for WS-RM support in this binding.

Since Http incurs additional latency above and beyond what is incurred by Tcp, this only leaves answer choice A.

http://msdn.microsoft.com/en-us/library/aa480191.aspx



Leave a Reply 0

Your email address will not be published. Required fields are marked *