Queued Message Handler - Revision history

Q at 14:59, 20 July 2021

2021-07-20T14:59:27Z

← Older revision		Revision as of 14:59, 20 July 2021
Line 1:		Line 1:
	The '''Queued Message Handler (QMH)''' ~~design pattern is~~ a combination of [[producer/consumer]], and [[Event Handler\|event handler]] architectures together. The producer loop, called the Event Handler Loop (EHL), contains an event structure that sends messages to the consumer loop, called the Message Handler Loop (MHL). The MHL receives and processes the messages. A message is enqueued when a UI event is triggered. The QMH can also be designed to provide feedback from the consumer to the producer using User Events.<ref>"Queued Message Handler Template" by National Instruments (http://www.ni.com/tutorial/53391/en/)</ref>		The '''Queued Message Handler (QMH)''' [[Design Patterns\|design pattern]] is a combination of [[producer/consumer]], and [[Event Handler\|event handler]] architectures together. The producer loop, called the Event Handler Loop (EHL), contains an event structure that sends messages to the consumer loop, called the Message Handler Loop (MHL). The MHL receives and processes the messages. A message is enqueued when a UI event is triggered. The QMH can also be designed to provide feedback from the consumer to the producer using User Events.<ref>"Queued Message Handler Template" by National Instruments (http://www.ni.com/tutorial/53391/en/)</ref>

	[[File:Queued Message Handler Design Pattern.png\|700x700px\|frameless\|center\|Queued Message Handler (QMH) with one Event Handler Loop (EHL) and one Message Handler Loop (MHL)]]		[[File:Queued Message Handler Design Pattern.png\|700x700px\|frameless\|center\|Queued Message Handler (QMH) with one Event Handler Loop (EHL) and one Message Handler Loop (MHL)]]

Q: Category reorg

2020-06-03T17:06:56Z

Category reorg

← Older revision		Revision as of 17:06, 3 June 2020
Line 42:		Line 42:
	<references />		<references />

	[[Category:Design ~~patterns~~]]		[[Category:Intermediate Design Patterns]]

Q: Added definitions and best practices

2020-05-04T13:45:42Z

Added definitions and best practices

@@ Line 2: / Line 2: @@
 [[File:Queued Message Handler Design Pattern.png|700x700px|frameless|center|Queued Message Handler (QMH) with one Event Handler Loop (EHL) and one Message Handler Loop (MHL)]]
 == Use Cases ==
 *[[Design Pattern Case Study: A Simple Counter#Queued Message Handler (QMH)|Comparison of Design Pattern showing QMH]]
 == References ==

Q: Added link

2020-04-30T13:00:13Z

Added link

← Older revision		Revision as of 13:00, 30 April 2020
Line 4:		Line 4:

	== Use Cases ==		== Use Cases ==
	~~Add yours here~~		*[[Design Pattern Case Study: A Simple Counter#Queued Message Handler (QMH)\|Comparison of Design Pattern showing QMH]]

	== References ==		== References ==

Q: Changed wording to match Design Pattern Overview page

2018-11-11T20:34:28Z

Changed wording to match Design Pattern Overview page

← Older revision		Revision as of 20:34, 11 November 2018
Line 1:		Line 1:
	The '''Queued Message Handler (QMH)''' design pattern is a combination of [[producer/consumer]], [[Event Handler\|event handler~~]] and [[state machine~~]] architectures together. The producer loop contains an event structure that sends messages to the consumer loop. The ~~consumer~~ receives and processes the messages ~~in a state machine~~. A message ~~can be~~ triggered ~~by UI events or from other states in the state machine~~. The QMH can also be designed to provide feedback from the consumer to the producer using User Events.<ref>"Queued Message Handler Template" by National Instruments (http://www.ni.com/tutorial/53391/en/)</ref>		The '''Queued Message Handler (QMH)''' design pattern is a combination of [[producer/consumer]], and [[Event Handler\|event handler]] architectures together. The producer loop, called the Event Handler Loop (EHL), contains an event structure that sends messages to the consumer loop, called the Message Handler Loop (MHL). The MHL receives and processes the messages. A message is enqueued when a UI event is triggered. The QMH can also be designed to provide feedback from the consumer to the producer using User Events.<ref>"Queued Message Handler Template" by National Instruments (http://www.ni.com/tutorial/53391/en/)</ref>

	[[File:Queued Message Handler Design Pattern.png\|700x700px\|frameless\|center\|Queued Message Handler (QMH) with one Event Handler Loop (EHL) and one Message Handler Loop (MHL)]]		[[File:Queued Message Handler Design Pattern.png\|700x700px\|frameless\|center\|Queued Message Handler (QMH) with one Event Handler Loop (EHL) and one Message Handler Loop (MHL)]]

Q: Added content from the FANDOM site.

2018-11-11T03:01:39Z

Added content from the FANDOM site.

New page

The '''Queued Message Handler (QMH)''' design pattern is a combination of [[producer/consumer]], [[Event Handler|event handler]] and [[state machine]] architectures together. The producer loop contains an event structure that sends messages to the consumer loop. The consumer receives and processes the messages in a state machine. A message can be triggered by UI events or from other states in the state machine. The QMH can also be designed to provide feedback from the consumer to the producer using User Events.<ref>"Queued Message Handler Template" by National Instruments (http://www.ni.com/tutorial/53391/en/)</ref>
[[File:Queued Message Handler Design Pattern.png|700x700px|frameless|center|Queued Message Handler (QMH) with one Event Handler Loop (EHL) and one Message Handler Loop (MHL)]]

== Use Cases ==
Add yours here

== References ==
<references />

[[Category:Design patterns]]