Pick a Silverlight RIA scenario [D2D, B2E, B2B, B2C] or choose a Web Services style [SOAP/RPC, XML/REST]

Browse by Tags

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, Read More...
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 Read More...
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 Read More...
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 Read More...
Silverlight scenarios for Rich Internet Applications
From the architecture described in the previous post a cup of Silverlight, a drop of Architecture , you may experience several technical requirements : Infrastructure Security DMZ (if the application is internet facing), Secured transport (HTTPS) if private Read More...
A cup of Silverlight, a drop of Architecture
We discussed before what Silverlight is about from a technical standpoint . Moving from theory to implementation, let's discuss today the architectural challenges when building a Silverlight App. The following considerations apply to Siliverlight 2 beta Read More...

Search

This Blog

Syndication

Page view tracker