Service Bus WSHttpRelayBinding

Posted: March 18, 2013 in WCF, Windows Azure

This is the fourth type of binding after the NetTcpRelayBinding, one of the binding of the Windows Azure Service bus. I previously introduced the Windows Azure Relay Binding with a small introduction about each binding. In this post you will be able to understand better how the WSHttpRelayBinding Namespace work. The WSHttpRelayBinding is nearly like the WsHttpBinding used in the .Net framework.

For the WsHttpBinding, it was available with the WCF 3.0. It is basically based on the SOAP 1.2 and enables more features like asynchronous messaging, message correlation, and transport-neutral addressing mechanisms which for sure adds some processing overhead, plus the support of both the transport level (SSL) and the message level (WS-Security).

The differences between the WSHttpRelayBinding and the WsHttpBinding is the creation and the control of a desirable creation of an endpoint on Windows Azure where you have the option to make it discoverable too.

For the URI Scheme, it doesn’t work as the NetTCPRelayBinding but you have to make the URI Scheme to “HTTP” or “HTTPS”

Unlike the NetTcpRelayBinding, the WSHttpRelayBinding is an interoperable binding. No matter what type of binding the other clients are using it works with them normally over the HTTP and the HTTPS protocols.

The WS2007HttpRelayBinding is the update of the WSHttpRelayBinding in several fields, like the security and the reliable session which I will certainly cover in a later blog posts.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s