This article is compatible with the latest version of Silverlight. This is part 1 of the series “Reactive Extensions in Silverlight”. 1.
Introduction to Reactive Extensions for .net In this Reactive Extensions (Rx) training course we will look at every piece in details in the upcoming videos. As MSDN defines it “The Reactive Extensions (Rx) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators. Using Rx, developers represent asynchronous data streams with Observables, query asynchronous data streams using LINQ operators, and parameterize the concurrency in the asynchronous data streams using Schedulers. Simply put, Rx = Observables + LINQ + Schedulers.” <p style="text-align:right;color:#A8A8A8"></p>
For a long time, good folks like Matt Podwysocki have extolled the virtues of Reactive Extensions (aka Rx) to me. It piqued my interest enough for me to write a post about it , but that was the extent of it. It sounded interesting, but it didn’t have any relevance to any projects I had at the time.
A Generic Class for Wrapping Asynchronous Begin/End Operations, Using Reactive Extensions for .NET (Rx)Introduction One of the patterns you will come across as a .NET programmer is the Begin/End pattern for making asynchronous function calls. The purpose of the pattern is to allow long-running operations to execute on a different thread than the calling thread, leaving the calling thread free (non-blocked) to continue execution. This is an important technique for building responsive GUIs, as well as for making remote calls effectively (whether you are calling a WCF service, using .NET remoting, accessing some REST-based Web Service, etc.).
Introduction The Rx Framework is a very interesting and useful library recently released via DevLabs . The purpose of the framework is to provide a large framework for working with the Observer pattern.
You have probably heard about Reactive Extensions , a library from Microsoft that greatly simplifies working with asynchronous data streams and allows to query them with LINQ operators. There are many different scenarios where using rx results in a much more simple and flexible code. This post demonstrates how to use Reactive Extensions for loading data from database asynchronously in chunks. The Problem Recently I had to load data from SQLite database in grid view but the query was taking long time as there were hundreds of thousands of rows and the query was doing like %search term% filtering.
I've been researching Reactive Extensions for the last few days, with an eye to writing a short section in chapter 12 of the second edition of C# in Depth. (This is the most radically changed chapter from the first edition; it will be covering LINQ to SQL, IQueryable, LINQ to XML, Parallel LINQ, Reactive Extensions, and writing your own LINQ to Objects operators.) I've watched various videos from Channel 9 , but today was the first time I actually played with it. I'm half excited, and half disappointed. My excited half sees that there's an awful lot to experiment with, and loads to learn about join patterns etc.
About the Reactive Extensions The Reactive Extensions (Rx) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators. Using Rx, developers represent asynchronous data streams with Observables , query asynchronous data streams using LINQ operators , and parameterize the concurrency in the asynchronous data streams using Schedulers . Simply put, Rx = Observables + LINQ + Schedulers.