Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Reactive extensions is another upcoming library for handling asynchronous programming, especially when it comes to composition of asynchronous events and methods.</p> <p>It's not native, however it's developed by Ms labs. It's available both for .NET 3.5 and .NET 4.0 and is essentially a collection of extension methods on the .NET 4.0 introduced <code>IObservable&lt;T&gt;</code> interface.</p> <p>There are a lot of examples and tutorials on their main site, and I strongly recommend checking some of them out. The pattern might seem a bit odd at first (at least for .NET programmers), but well worth it, even if it's just grasping the new concept.</p> <p>The real strength of reactive extensions (Rx.NET) is when you need to compose multiple asynchronous sources and events. All operators are designed with this in mind and handles the ugly parts of asynchrony for you.</p> <p>Main site: <a href="http://msdn.microsoft.com/en-us/data/gg577609" rel="nofollow">http://msdn.microsoft.com/en-us/data/gg577609</a></p> <p>Beginner's guide: <a href="http://msdn.microsoft.com/en-us/data/gg577611" rel="nofollow">http://msdn.microsoft.com/en-us/data/gg577611</a></p> <p>Examples: <a href="http://rxwiki.wikidot.com/101samples" rel="nofollow">http://rxwiki.wikidot.com/101samples</a></p> <p>That said, the best async pattern probably depends on what situation you're in. Some are better (simpler) for simpler stuff and some are more extensible and easier to handle when it comes to more complex scenarios. I cannot speak for all the ones you're mentioning though.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload