Search

1. Introduction

In the first part of the article, I tried to describe what is RX Framework and what can be done with it. One thing I’ve missed to mention was how RX could be used for asynchronous service calls. Namely, this is the accent in the second part of the article. For those who missed the first part, you could read it here.

The demo source code could be downloaded from here.

If you haven’t heard of Reactive extensions (Rx) for .NET, it’s time to get familar. Rx is extremely cool and once you understand it, it will change the way you write client-side code forever. Instead of providing an overview of Rx, I’m going to urge readers to check out Pencho Popadiyn’s blog post, where he does a much better job of explaining it that I probably could.

1. Introduction

Beta versions of Silverlight 4 and .NET Framework 4 are already a fact. There are just a few weeks until the official releases. One of the coolest features which will be part of .NET Framework 4 and also will be available for Silverlight applications is the RX Framework. The arising interest around the RX Framework made me roll up my sleeves and start playing around this.
So the first step was to answer several important questions such as: “what is Linq to Events?”, “what is RX Framework?”, and “what is Reactive Programming?” And generally what lies behind these sound terms? Linq to events or RX Framework (also known as Reactive Extensions for .NET Framework) is one and the same designation for a library for composing asynchronous and event-based programs using observable collections.