Home > Net > C # for advice about the difference between event-driven and message driven and use cases
C # for advice about the difference between event-driven and message driven and use cases
Time:11-21
In the project before, for data, sometimes using polling to monitor changes, then in the BBS often see sp1234 elder said asynchronous, event-driven and slowly learning, events, INotifyPropertyChanged... Gradually understand and use, the feeling on the program logic and reason are more scientific, then expand the message-driven, find the related information and the difference between event-driven and message-driven online, always feel in the clouds and fogs, there are a lot of people said no distinction, I personally feel event is the message encapsulation, specific what is still uncertain, so consult guidance of predecessors, the difference between event-driven and message driven, and where, more scientific project in which way? Thank you for the
CodePudding user response:
I personally feel, like just semantics,
As production, consumption patterns, a message out, trigger consumers subscribe to events, The whole a message-driven or event driven, in fact, in my opinion, is no problem,
Feel it's like discussing "back" of the four kinds of writing
CodePudding user response:
New winform, drag a button, double click on the button to generate an event, click on the button, the button will perform, about the meaning of