Adoption of WCF technologies in Silverlight 2 applications on the web

Hero Image

Microsoft Silverlight 2 is the first version of the .NET client development platform which contains Windows Communication Foundation (WCF) components. The Silverlight platform in this version is primarily targeting rich internet application development. Such applications execute in a security sandbox that limits the choices for data exchange with the outside world. For example, a Silverlight application does not have free access to the file system except for an isolated local storage. Any Silverlight application that requires external data must use a communication mechanism to obtain it from the web and a serialization mechanism to parse and manipulate the data. Silverlight 2 offers several communication and data serialization technologies that facilitate these scenarios.

The choice of communication and serialization components in Silverlight 2 was based on developer community data and the target scenarios for the platform. Some time after the platform has shipped in October 2008 I decided to measure the level of adoption of the various technologies we added to Silverlight 2. We intended to use this data to validate our original assumptions as well as inform future releases.

The methodology of this measurement was based on finding a statistically significant sample of Silverlight 2 applications deployed on the web and statically analyzing these applications to identify the platform features they use. I was interested in several communication technologies:

  • WebClient
  • HttpWebRequest
  • ClientBase (WCF proxy)
  • ChannelFactory (direct use of WCF)
  • Sockets
  • Polling duplex
  • Astoria

I was also looking for several serialization technologies:

  • DataContractSerializer
  • DataContractJsonSerializer
  • XmlSerializer
  • JsonValue
  • Syndication
  • XElement
  • XmlReader

Lastly, I was interested in the backend technology of services the clients were communicating with (ASMX, WCF, or other), as well as whether these calls were same-domain or cross-domain.

In February 2009 (about 5 months after Silverlight 2 released) I used a custom web crawl engine to index over 40,000 web pages, which yielded 772 Silverlight 2 applications across 335 web sites. Then I downloaded and disassembled the managed application code from the XAP into IL to statically analyze it for sentinel constructs of the technologies in question. I discuss the results below.

The high level findings are as follows:

  • 53% of applications used one or more of the communication technologies
  • 47% of applications used one or more of the serialization technologies (counting only direct use by the application code; this number does not include indirect use via other components, e.g. a WCF proxy)
  • 41% of applications used neither communication or serialization technologies

The fact that over half of all Silverlight applications used at least one communication technology emphasizes the importance of the communication component in a sandboxed web application.

The table below contains the breakdown of the adoption of individual communication technologies across applications that use at least one of the communication technologies (i.e. across the 53% of Silverlight 2 applications I found through the web crawl).

RankAdoptionTechnology
163.6%WebClient
244.9%ClientBase (WCF proxy)
318.0%HttpWebRequest
42.2%Socket
51.7%Astoria
60.7%ChannelFactory (WCF)
70.2%Polling duplex

Similarly, the table below contains the serialization technology adoption breakdown across application that use at least one of the serialization technologies (i.e. across the 47% of Silverlight 2 applications I found through the web crawl). The number represents only direct use of these serialization mechanisms by the application code. In particular, it excludes indirect use by web service proxies like ClientBase (WCF) the application may be using.

RankAdoptionTechnology
170.3%XElement
243.5%XmlReader
38.8%XmlSerializer
46.9%DataContractJsonSerializer
53.2%DataContractSerializer
61.9%JsonValue
71.6%Syndication

WebClient is the mostly adopted communication technology, followed by the WCF proxy (ClientBase). WebClient is mainly used to download entire files or loosely structured XML data, which is later processed using XElement as a serializer of choice. WCF is primarily used as a mechanism to access strongly typed data. One aspect to note is that WCF proxy internally uses DataContractSerializer (another WCF technology) as a default serialization engine (something WebClient is not doing with XElement), which means that DataContractSerializer has a total adoption of around 25.3% across all surveyed Silverlight 2 applications (47% * 3.2% + 53% * 44.9%; this assumes no overlap between applications using DataContractSerializer directly and ClientBase at the same time, which is an approximation).

Analysis of the backend technology of the services that Silverlight 2 clients are communicating with indicates 52% of them are based on WCF technology, 42% are based on ASMX, and the technology of the remaining 6% could not be determined. Furthermore, analysis of the URLs of the web service calls indicates 68% of calls is cross-domain while only 32% are same-domain. The large share of cross-domain calls is an interesting finding in itself. It also seems to support a hypothesis that the (still) large share of ASMX as the backend technology has to do with the existence of legacy services.

Overall the data from this research informed several decisions related to investments in subsequent releases of Silverlight, but this is another story. As a matter of fact Silverlight 3 is coming out within hours of this writing, check out http://www.microsoft.com/silverlight/ for an announcement.


ArrowPrevious
NextArrow

Most Recent

23 June 2022
Is EdgeDB the Future?

EdgeDB solves some design flaws of relational and No-SQL databases. Read the differences between EdgeDB, MongoDB, and GraphQL and the best use cases for EdgeDB.

22 June 2022
Trello API Limits, 5 Best Practices to Avoid Rate Limiting

Third-party APIs like the Trello API can make life easier for developer. We'll discuss best practices to avoid rate limits in the Trello API.

22 June 2022
Using the Google Calendar API in React.js, An In-Depth Guide

We'll build a simple React app that uses Google Calendar API and that lists and adds events to your calendar. Let’s dive in.