SALES: 1-800-867-1380

Creating a REST-based Client Application for Service Bus

Updated: August 26, 2015

A client application can access a REST-style service by using the WebHttpRelayBinding binding, or by directly sending HTTP requests to the service endpoint.

Some applications, such as browsers or JavaScript applications, do not use the Microsoft.ServiceBus.dll assembly. These applications can access a REST service endpoint directly using whatever HTTP capabilities available to them. In this case, the only issue is what type of security and authentication the service requires. However, in this type of scenario, it is common for the service to require little or no authentication. For more information, see How to: Create a REST-based Service that Accesses Service Bus. For a full example of this scenario, see the WebHttp sample in the Service Bus Samples, or the REST Tutorial for AppFabric Service Bus.

If the client has access to the Azure SDK, it follows the same procedure as a standard Service Bus client application. For more information, see How to: Create a WCF SOAP Client Application for the Service Bus. The only unique feature in this scenario is that attributes such as [WebGet] are applied to the contract you retrieve from the service. These attributes map the contract to the REST standard. Because it is an Internet-based protocol, you are required to use an HTTP-based binding, such as WebHttpRelayBinding.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft