Hi guys - I'm working on writing a technical book about the Reactive Extensions along with Jesse Liberty, and we'd like to get your feedback on what you would like to see in a book on Rx. We're definitely going to cover all of the basics - marble diagrams, operators, etc, but we definitely would like to get a better grasp on what people are interested in using Rx for.
What domains are you folks using Rx for / would be interested in? We definitely see the usage in finance applications as well as WPF/Silverlight programming, but we're also interested in other problem domains that you folks are working on - any feedback would be great!
I find Rx to be quite useful and powerful in general for consuming and hosting web services, especially simple RESTful APIs. As a client, often I find myself needing to combine the results of several service calls into a single stream of data, while keeping things async, buffering the data so it may be shared by multiple subscribers, and also handling various service fault types by including prescribed retry logic. Writing all of this in LINQ-style queries and producing a result that is a simple IObservable<T> is quite elegant.
Also, don't forget to include IQbservable, although I don't have any specific examples of it yet.
I'm using RX in plain old WPF UI :) Example is here :
- feel free to borrow.
In my opinion, perfect book on RX should pay a great deal of attention to not-so-evident parts of RX. Combinators and marble diagrams are great, but it is easy enough to grasp, especially if you were exposed to LINQ. Side effects of subscriptions, hot and cold observables, role of completion, different subjects and their differences, scheduler, .Create and .CreateWithDisposable - all these are necessary prerequisites for correct RX usage, yet are difficult to get right.
That's great news.
I wrote Windows Phone 7 App using Rx(Microsoft.Phone.Reactive).
This is lyric browser.
Rx showed power for an event handling of the music player information.
In using "Throttle" for consecutive play and the adjustment of the async request.
In addition, I feel that it is a merit that a unit test with Moles becomes easy because Rx can wrap an event.
My article of combination with Moles.
(sorry, this blog is written in Japanese.)
I'm glad when written about the easiness of the unit test with rx and how to.
My WP7 app Utakotoha is simple application.
But the combination with UI is considerably terrible, ugly.
I describe UI in XAML, after all I cannot avoid the cooperation with the MVVM pattern and think that the one goes well.
Therefore, My request is "Rx and UI", "MVVM and Rx".
I want the answer of this theme.
// The theme is taken up with your recent blog, thanks.
other, There are the library which I made...
This is OAuth Library that request returns IObservable.
Rx has high affinity for streaming API.
Main technology feature is AsynchronousExtensions.cs
I think plain Rx lack for async easily.
Rx needs wrapped-tier like Async CTP(AsyncCtpLibrary.dll).
Is it ClientProfile.dll/ExtendedProfile.dll?
It just began, not yet enough.
I cooperate with RxJS by adding binding to bundle it with.
and this package contains IntelliSense(rx-vsdoc.js) generator.