Link to Events Saved my life. (Rx and Reactive Extensions)
<p> </p> <p> I’m pleased to announce a preview of the <a href="http://msdn.microsoft.com/en-us/devlabs/ee794896.aspx" mce_href="http://msdn.microsoft.com/en-us/devlabs/ee794896.aspx">Reactive Extensions for .NET (Rx)</a> on MSDN DevLabs.</p> <p> <a href="http://canyons.ocbsa.org/aaRxDemo.zip">Download Rx Demos and Slides!</a></p> <p> Using Rx, programmers can write succinct declarative code to orchestrate and coordinate asynchronous and event-based programs based on familiar .NET idioms and patterns. Rx has a strong theoretical basis by using the duality between the classic Iterator and Observer design patterns to simplify controlling asynchrony. By combining the expressiveness of LINQ with the elegance of category theory, Rx allows programmers to write asynchronous code without performing cruel and unnatural acts.</p> <p> </p> <p> As the name implies, reactive programs react to changes in their environment. Traditionally, programmers use locks and event handlers to coordinate these changes. Rx models asynchronous computations and events as push-based, or observable, collections, thus expanding the scope of the standard LINQ sequence operators and extension methods beyond the familiar pull-based, or enumerable, collections into the realm of reactive programming.</p>
Brice Ulwelling
Silverlight | Rx | Reactive Extensions | C#
Mobile Home
Sessions
Schedule
Presenters
Rooms
Login