MSDN Magazine - July 2008 - (Page 60)

Now create the Contoso Classifieds Authority. This will hold general configuration information in the system SSDSClient.Authority contosoAuth = new SSDSClient.Authority(); contosoAuth.Id = "contosoclassifieds"; and submit the creation to SSDS ssdsProxy.Create(serviceScope, contosoAuth); Now that the main Contoso Classifieds Authority has been created, point your scope to it, then create the container to hold the cities you will be serving classified ads to, and submit the container creation to SSDS: serviceScope.AuthorityId = contosoAuth.Id; SSDSClient.Container citiesContainer = new SSDSClient.Container(); citiesContainer.Id = "Cities"; ssdsProxy.Create(serviceScope, citiesContainer); Figure 4 Classifieds App Administrative Client There are a few reasons I went with this design. I chose to implement on authority per city so that I can ensure the authority is provisioned in a datacenter that is geographically close to the population it will serve. I chose one container per listing category so that I have a simple query pattern and I can spread the load across multiple machines in the cluster (remember a container is scoped The process to create a container is similar to the process of creating an authority. The only difference is that you create a Container object instead of an Authority object and, instead of an empty scope, you update the scope to point to the authority in which the container is to be created. Create the container that will hold all the Header and Listing categories you will support within the application: SSDSClient.Container categoriesContainer = new SSDSClient.Container(); categoriesContainer.Id = "Categories"; ssdsProxy.Create(serviceScope, categoriesContainer); It is up to the developer to create any authorities, containers, and entities. to a specific node in the back-end cluster). Figure 4 shows the user interface for the Contoso Classifieds Administration client. As previously mentioned, it is up to the developer to create any authorities, containers, and entities the application will use. In the sample app, all this work is contained within the click event for the Perform Initial Setup button. (The full code, including error handling, is included in the code download for this article.) Provisioning an SSDS authority is extremely easy. In this example code I use the SitkaSoapServiceClient, for which I had previously added a service reference to the SSDS SOAP interface: using (SSDSClient.SitkaSoapServiceClient ssdsProxy = new SSDSClient.SitkaSoapServiceClient()) Once the authority is created you can point a Web browser to it, using either HTTP or HTTPS, and you can view the container’s contents using the REST interface. Simply use the new DNS name that SSDS created when setting up the authority. In this case, the URL would be: http://contosoclassifieds.data.data.beta.mssds.com/v1 After this URL is entered into the browser, you will be prompted to authenticate. Once you successfully authenticate, you will see something like this in your browser: contosoclassifieds 11 You have already seen an Authority, but what is an SSDS scope? The scope object is used within SSDS to provide a way of addressing objects in the SOAP service similar to the way URIs are used in the REST service. The first thing you should do is set the user name and password for the service: ssdsProxy.ClientCredentials.UserName.UserName = txtUserName.Text; ssdsProxy.ClientCredentials.UserName.Password = txtPassword.Text; The authority name is lower-cased because since SSDS creates a DNS entry for the authority, you are required to follow DNS naming conventions. After creating the container, if you refresh the browser and add an empty query to your URL in the form of ?q=””, you will see a single Container object being returned in the EntitySet. An EntitySet is simply a collection of entities that are returned as the response to a query. Upon completion of initial setup the sample application will have created one authority (contosoclassifieds) and two containers (Categories and Cities): Categories 1 You need to create an authority, which is at the highest level of the ACE model, so you first create an empty scope: SSDSClient.Scope serviceScope = new SSDSClient.Scope(); 60 msdn magazine SQL Server Data Services

Table of Contents Feed for the Digital Edition of MSDN Magazine - July 2008

MSDN Magazine - July 2008 Contents Toolbox CLR Inside Out Flex Your Data Data Points Advanced Basics Office Space Cutting Edge Data Services ADO.NET Data and WPF Transactions WCF P2P Test Run Security Briefs Foundations .NET Matters {End Bracket}

MSDN Magazine - July 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.