Book Image

Reactive Programming for .NET Developers

Book Image

Reactive Programming for .NET Developers

Overview of this book

Reactive programming is an innovative programming paradigm focused on time-based problem solving. It makes your programs better-performing, easier to scale, and more reliable. Want to create fast-running applications to handle complex logics and huge datasets for financial and big-data challenges? Then you have picked up the right book! Starting with the principles of reactive programming and unveiling the power of the pull-programming world, this book is your one-stop solution to get a deep practical understanding of reactive programming techniques. You will gradually learn all about reactive extensions, programming, testing, and debugging observable sequence, and integrating events from CLR data-at-rest or events. Finally, you will dive into advanced techniques such as manipulating time in data-flow, customizing operators and providers, and exploring functional reactive programming. By the end of the book, you'll know how to apply reactive programming to solve complex problems and build efficient programs with reactive user interfaces.
Table of Contents (15 chapters)
Reactive Programming for .NET Developers
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface

Sourcing from CLR events


An event is the occurrence of something we can handle somehow with our code. More precisely, in .NET, an event is a kind of Delegate object, an object that represents one or multiple actions to run. The Delegate object is the .NET implementation of the Observer pattern with the addition of other features, such as asynchronous execution.

By convention, any event in .NET uses the Delegate implementation specific to System.EventHandler or any other childhood according to the inheritance tenet. This implementation accepts handlers (subscribers) that must accept two parameters, such as the following example:

static void EventHandler1(object o, EventArgs e) 
{ 
    Console.WriteLine("Handling for object {0}", o); 
} 

In place of using the generic EventArgs type as an event parameter as specified by the EventHandler delegate, when using the related generic version EventHandler<T>, we can use any other type as an argument parameter.

By using reactive...