thanks for the great video. Looks like the *event* mode also performs the similar Observer Design Pattern job, could you let us know the benefit of using the IObservable/IObserver interface?
@William Liu, the main benefit of IObservable/IObserver implementation is that the entire registration between the subject and the observer relationship is invested. And that provides an opportunity to further decouple the two. So we can create a separate event manager class that can manage the relationship between the subject (IObservable) and the observer (IObserver).
Your vids are awesome.But if you could show some diagrams to explain the notion behind a concept that would make your tutorials even more appealing.
thanks for the great video. Looks like the *event* mode also performs the similar Observer Design Pattern job, could you let us know the benefit of using the IObservable/IObserver interface?
@William Liu, the main benefit of IObservable/IObserver implementation is that the entire registration between the subject and the observer relationship is invested. And that provides an opportunity to further decouple the two.
So we can create a separate event manager class that can manage the relationship between the subject (IObservable) and the observer (IObserver).
@@DotNetCoreCentral Thank you for clarifying it!
Thanks for the nice content. By the way, internal is the default if no access modifier is specified in c# not private.
For classes the default is internal. For class members the default is private.