Messenger Library Messaging Patterns - Revision history

Drjdpowell: Added GDevCon1 talk link

2019-02-19T20:08:59Z

Added GDevCon1 talk link

← Older revision		Revision as of 20:08, 19 February 2019
Line 10:		Line 10:
	Useful Links:		Useful Links:
	* [https://www.enterpriseintegrationpatterns.com/patterns/messaging/index.html Enterprise Integration Patterns]		* [https://www.enterpriseintegrationpatterns.com/patterns/messaging/index.html Enterprise Integration Patterns]
			* [https://youtu.be/HIuzY_Bs7BI GDevCon1 talk that includes messaging patterns]

	[[Category:Messenger Library]]		[[Category:Messenger Library]]
	[[Category:Design patterns]]		[[Category:Design patterns]]

Drjdpowell at 14:40, 19 February 2019

2019-02-19T14:40:16Z

← Older revision		Revision as of 14:40, 19 February 2019
Line 12:		Line 12:

	[[Category:Messenger Library]]		[[Category:Messenger Library]]
			[[Category:Design patterns]]

Drjdpowell at 17:59, 18 February 2019

2019-02-18T17:59:01Z

← Older revision		Revision as of 17:59, 18 February 2019
Line 2:		Line 2:

	[[Messenger Library]] is intended to support the following patterns:		[[Messenger Library]] is intended to support the following patterns:
	* Command: simply sending a command [[Messenger Library Messages\|message]] to an [[Messenger Library ~~Address~~\|Address]].		* Command: simply sending a command [[Messenger Library Messages\|message]] to an [[Messenger Library Addresses\|Address]].
	* Request-Reply (blocking): sending a command and then waiting for a specific replay to come back. Also called a "Query".		* Request-Reply (blocking): sending a command and then waiting for a specific replay to come back. Also called a "Query".
	* Request-Reply Asynchronous: Sending a request with reply address attached to the message, then carrying on with other work before the reply is sent back to us. This is analogous to email.		* Request-Reply Asynchronous: Sending a request with reply address attached to the message, then carrying on with other work before the reply is sent back to us. This is analogous to email.

Drjdpowell at 17:58, 18 February 2019

2019-02-18T17:58:25Z

← Older revision		Revision as of 17:58, 18 February 2019
Line 7:		Line 7:
	* Scatter Gather (Blocking or Async): multi-actor versions of Request-Reply. Makes use of Future Tokens.		* Scatter Gather (Blocking or Async): multi-actor versions of Request-Reply. Makes use of Future Tokens.
	* Register-Notify: Registration messages request future update "Notifications". See the Observer Registry helper object.		* Register-Notify: Registration messages request future update "Notifications". See the Observer Registry helper object.

			Useful Links:
			* [https://www.enterpriseintegrationpatterns.com/patterns/messaging/index.html Enterprise Integration Patterns]

	[[Category:Messenger Library]]		[[Category:Messenger Library]]

Drjdpowell: Messenger Library Messaging Patterns

2019-02-18T17:55:00Z

Messenger Library Messaging Patterns

New page

== Messaging Patterns ==

[[Messenger Library]] is intended to support the following patterns:
* Command: simply sending a command [[Messenger Library Messages|message]] to an [[Messenger Library Address|Address]].
* Request-Reply (blocking): sending a command and then waiting for a specific replay to come back. Also called a "Query".
* Request-Reply Asynchronous: Sending a request with reply address attached to the message, then carrying on with other work before the reply is sent back to us. This is analogous to email.
* Scatter Gather (Blocking or Async): multi-actor versions of Request-Reply. Makes use of Future Tokens.
* Register-Notify: Registration messages request future update "Notifications". See the Observer Registry helper object.

[[Category:Messenger Library]]