"Azure Services Platform Step by step-6th" Introductory example of Service bus

Friends who do not have the Microsoft. NET Services (Dec 2008 CTP) SDK installed directly download the attached article.

Usages:

First, open the visual in the Microsoft. NET Services (Dec 2008 CTP) SDKSamplesServiceBusGettingStartedEchoCS35 Directory Studio Solution EchoSample.sln

The picture is not clear? Please click here to view the original image (larger).

Right-click on the service item to enable the new instance.

Enter the user name and password for the scenario. When validation succeeds (set in http://portal.ex.azure.microsoft.com), the console gives a URI similar to "Sb://servicebus.windows.net/services/sixsix/echoservice".

The picture is not clear? Please click here to view the original image (larger).

Then enable a client-side debugging instance. Also requires that you enter a solution name and password.

The picture is not clear? Please click here to view the original image (larger).

At this point the client already connected to the service side of the service.

I believe that through the solution name already know the role of the service, very simple, is the customer segment input string to the server, the server to the client back to the same string.

The picture is not clear? Please click here to view the original image (larger).

What is the use of service Bus by example:

Obviously, the service used in this example is the most basic echo service in network programming. We used the Username/password authentication method.

Readers can try to turn off the server. You will find that there is no change in the client, just no more calls to the service, no echo. This shows that the service bus actually played a bridging role. Server-side program no matter how the network environment, whether in the NAT or public environment, also do not care how the service IP changes, or even the service behind the firewall, the client's positioning depends on service bus to provide the unified Uri,service Bus provides registration and address resolution for the service. In this case, the Echo service's address is always "sb://servicebus.windows.net/services/sixsix/echoservice/," and the actual network environment and geographic location of the service are completely transparent to the client. This is a practical cow x function of Service bus mentioned in the previous section.

In addition, if you open Http://servicebus.windows.net/services/{your solution name}/, you can see that the service bus solution you under Atom 1.0 The feed is formatted in "Bus" (showing only the services that are currently available, that is, if you turn off the server program, you will not see the content). The screenshot below shows the http://servicebus.windows.net/services/sixsix/. "Sixsix" is my solution name. At present there are only 1 echoservice under this solution.

The picture is not clear? Please click here to view the original image (larger).

Understand the service bus usage and purpose, the programming operation is very easy. Check the code yourself.