Is it possible to replace traditional event handling in C# with the new Reactive framework?

Question

All examples on System.Reactive.dll I've seen so far deal with Events, EventArgs and EventHandlers, I wonder whether someone can show me an example where event notification is handled without this.

For instance, in Microsoft's XNA framework, you have a static method called Mouse.GetState() which will return the current MouseState (with mouseState.LeftButton == ButtonState.Pressed you could see whether the left button is pressed, for instance). So there are no EventArgs, Events etc. in the first place and I think this could serve as an example of achieving event notification without introducing the concept of an event at all.

Could System.Reactive be of help here? Can anyone wrap this into an example with System.Reactive?

Answer 1

Quote from an article that I found helpful:

In C#, a programmer uses reactive programming whenever he specifies a call-back for an asynchronous operation or a handler for an event. When the asynchronous operation finishes or when the handled event takes place, a method gets called and executed as a reaction to the event.

Mouse.GetState() is a method that gets the current state of the Mouse. Reactive programming would be useful if you were trying to continuously handle (react to) changes to the state of the mouse.

For example, you could create a wrapper that continuously polls the mouse state, and then notifies its observers (essentially back to publishing events here). You could then write code to handle (react to) those updates.

Answer 2

Polling mouse or keyboard states works in a game where you have direct access to update methods that are the heartbeat of the application. The update method IS your event that is called and passed on to many objects, not much different to MouseDown. So even here you do rely on the observer pattern.