Observer Design Pattern (An Introduction for .NET Developers [.NET 6 and C# 10])

Подписаться 27 тыс.

Просмотров 5 тыс.

50% 1

The observer pattern is a Behavioral design pattern.
The main intent of the pattern is to define a one-to-many dependency between objects so that when one object changes its state, all objects dependent on it are notified automatically.
The previous two videos in this Design Pattern series are:
1. Factory method design pattern: • Factory Method Design ...
2. Abstract factory design pattern: • Abstract Factory Desig...
3. Builder design pattern: • Builder Design Pattern...
4. Prototype design pattern: • Prototype Design Patte...
5. Adapter design pattern: • Adapter Design Pattern...
6. Bridge design pattern: • Bridge Design Pattern ...
7. Decorator design pattern: • Decorator Design Patte...
8. Façade design pattern: • Façade Design Pattern ...
9. Flyweight design pattern: • Flyweight Design Patte...
10. Proxy design pattern: • Proxy Design Pattern (...
11. State design pattern: • State Machine and Stat...
12. Command design pattern: • Command Design Pattern...
13. Iterator design pattern: • Iterator Design Patter...
My GitHub URL: github.com/choudhurynirjhar
My Blogsite URL: dotnetcorecentral.com/

Наука

Опубликовано:

25 дек 2021

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 6

@F2H16 2 года назад

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.

@F2H16 2 года назад

Thanks for the nice content. By the way, internal is the default if no access modifier is specified in c# not private.

@paulembleton2936 Год назад

For classes the default is internal. For class members the default is private.

@williamliu8985 2 года назад

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?

@DotNetCoreCentral 2 года назад

@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).

@williamliu8985 2 года назад

@@DotNetCoreCentral Thank you for clarifying it!