Tip : Cross Domain Policy when Self-Hosting your Services

This tip is about self hosting of services with the .Net WCF or Java Restlet framework. Cross-domain access is mandatory here since the Site of Origin does not host the services. Self hosting a service represents a quick & easy way to expose a Web Service for tests purpose. Yet, customization is extermely limited since self hosting does…

1

How-To : Silverlight accessing Java REST services (Part 2 – No Cross Domain : Tomcat/Eclipse)

The HowTo serie demoes Silverlight accessing Web Services in various configuration. In this post, we will demonstrate a REST service consumed by a Silverlight client application where the Site of Origin hosts the Web Services. This scenario is categorized as a D2D scenario without cross-domain policy. The XAP package, the REST service Eclipse project and…

3

How-To : Silverlight accessing Java SOAP services (Part 1 – Cross Domain : IIS + Tomcat)

The How-To series demo Silverlight accessing Web Services in various configuration. In this post, we will demonstrate a SOAP service consumed by a Silverlight client application. This scenario can be categorized as a D2D scenario with a cross domain policy. Both the Silverlight and SOAP service are available as an attachment to this post. Since…

3

B2C scenario : Customer Environement

The B2C scenario corresponds to Web applications accessed by customers, traditionnaly built with some dynamic HTML/AJAX technology running on the server side, that have been elected to leverage the Silverlight capabilities (enriched user experience, vector based contents, scaling, rich media…).To comply with the scope of this blog, we’ll concentrate on RIA scenarios, where the customer…

2

Cross Domain : Trouble while accessing Web Services

When Silverlight attempts to access a Web Service, if the SOO is different from the Web Service host, you have to deal with a cross domain issue. This issue can occur in various scenarios as described in Silverlight scenarios for Rich Internet Applications The issue can be treated as follow : 1.  I am encountering…

3

B2B scenario : Partner Environment

The B2B scenario corresponds to Enterprise Web Services exposed to a partner through a Rich Client application, traditionnaly built with some dynamic HTML/AJAX technology running on the server side, that have been elected to leverage the Silverlight capabilities (enriched user experience, vector based contents, scaling, rich media…). As listed in Silverlight scenarios for Rich Internet…

4

B2E scenario : Intranet Environment

The B2E scenario corresponds to internal Web applications, traditionnaly built with some dynamic HTML/AJAX technology running on the server side, that have been elected to leverage the Silverlight capabilities (enriched user experience, vector based contents, scaling, rich media…). As listed in Silverlight scenarios for Rich Internet Applications, the following constraints apply to the Intranet Environment…

1

How-To : Silverlight accessing Java REST services (Part 1 – Cross Domain : IIS + Tomcat)

The HowTo serie demoes Silverlight accessing Web Services in various configurations. In this post, we will demonstrate a REST service consumed by HTTP GET and POST requests issued from a Silverlight client application. This scenario can be categorized as a D2D scenario with a cross domain policy. The Silverlight example described below is available as…

1

Limitations when accessing REST services from Silverlight

As explained in What are those SOAP/RPC and XML/REST styles ?, the REST support in Silverlight has several limitations : Only the “Content-Type” HTTP header can be accessed from the Silverlight client code. The WebClient works fine in most scenarios, yet turn to HttpWebRequest if you need to control the response flow. HTTP methods are limited to…

2

What are those SOAP/RPC and XML/REST styles ?

In the Silverlight world, the sole protocol you need to care about is the HTTP protocol. Yet, you can take 2 directions to send and retreive messages from a Silverlight Rich Client application. The SOAP/RPC style leverages the SOAP specifications and the Remote Procedure Call paradigm (ie, a request message is composed of an operation…

4