{"id":531,"date":"2009-11-27T20:45:16","date_gmt":"2009-11-27T19:45:16","guid":{"rendered":"http:\/\/www.minddriven.de\/?p=531"},"modified":"2009-11-28T15:34:51","modified_gmt":"2009-11-28T14:34:51","slug":"news-on-rx-reactive-extensions-for-net","status":"publish","type":"post","link":"https:\/\/www.minddriven.de\/index.php\/technology\/dot-net\/news-on-rx-reactive-extensions-for-net","title":{"rendered":"News on Rx (Reactive Extensions for .NET)"},"content":{"rendered":"

\"Rx<\/a>As written<\/a> before the Reactive Extensions for .NET (Rx, aka „Reactive Framework“) have been published as pre-release on their own DevLabs<\/a>-site. The Rx-team is asking for feedback from you as developers and will include improvements into timely released development packages, until they’ll ship the final pieces with .NET 4.0. Check out the MSDN forum<\/a> to give your feedback or ask for support.<\/p>\n

So what’s new in Rx compared to the early DLL from the Silverlight 3 toolkit sources?<\/p>\n

In general, many improvements were made on the API and functionality<\/strong>: methods on the Observable<\/code> class have been rearranged and extended to give you full flexibility in many use cases. One method that I really love is Throttle()<\/code><\/strong>. Imagine that you have a textbox and everytime the user makes an input (without pressing Return) a data source is queried for items that match this input in some way (e.g. filtering by name or something). Now you discover that you’ve got performance issues. The search is done as the user types the first character and that’s not what you want. You only want to react to user’s input if he isn’t typing anything for -let’s say- 1 second. Throttle()<\/code> solves this for you by one method call, you do not need anything else or do something manually. That’s great! Try to develop this with common event-based programming and you know what I mean…<\/p>\n

Then the Rx-team intends to converge <\/strong>the functionality of IEnumerable and IObservable. IObservable has much of the functionality of IEnumerable and LINQ operators make composing, filtering and transformation of event streams very simple and intuitive. And in the DevLabs-release of Rx the Rx-team is moving some functionality from IObservable (such as the Amb()<\/code> method) to IEnumerable as well. If you need it or not: this is leveraging the dualism of both concepts for developers and makes both interfaces more intuitively usable.<\/p>\n

Furthermore the ground base of Rx is now Px (or PFx), the Parallel Extensions<\/strong> for .NET that will be part of .NET 4.0 as well. For every concurrent operation Px is taken and does the whole work (by creating a Task<T><\/code>). As a side effect of supporting Rx for .NET 3.5 SP1, the Rx-team has back-ported Px from .NET 4.0 to .NET 3.5 SP1 and made it usable for this platform as well. Great job!<\/p>\n

One thing very cool and worth to mention are Subjects <\/strong>as new components in Rx. Subjects implement the type ISubject<S,T><\/code> and are kind of hybrids between IObserver<S><\/code> and IObservable<T><\/code>. A Subject implements both IObservable<\/code> and IObserver<\/code> and can be seen as „channel“ or „transforming storage“. The channel behavior is that you can push values as input<\/em> into the subject via the IObserver<\/code> methods (OnNext()<\/code>, OnCompleted()<\/code> and OnError()<\/code>) and that you can subscribe to the Subject via the IObservable.Subscribe()<\/code> method to get the output<\/em> from the Subject. The Subject itself can do some transformation<\/em> with the values that are pushed into it, can store the values and is able to take responsibility of what happens if someone subscribes to it. Subjects act as storage<\/em> as well. When values are flowing into the Subject it can store them (or only the last or some transformed value, …) and when someone subscribes it can return all stored values (or only the last etc.). That means that e.g. an asynchronous operation needs not to be executed multiple times when using Subjects. The return value is stored in the Subject and can be extracted everytime a client subsribes to the Subject (independent of the moment of the subscription).
\nDependent on the intent of the Subject, Rx comes with several implementations that differ in their transformation and output behavior:<\/p>\n