Included Subscriber Publisher communication scheme as a standard way for communicating outside the tree hierarchy.

[PrimaryKey]

Please add to AF:

Included Subscriber Publisher communication scheme as a standard way for communicating outside the tree hierarchy. 

https://forums.ni.com/t5/Actor-Framework-Documents/Event-Source-Actor-Package/ta-p/3538542?profile.l...

[AristosQueue (NI)]

This idea will be declined for the same reason as this other, related idea:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Ability-to-Get-Actor-Enqueuer-by-Path/idc-p/3989884/h...

[Darren]

Declined for reasons listed here: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Ability-to-Get-Actor-Enqueuer-by-Path/idc-p/3989884/h...

[drjdpowell]

Note: Subscriber-Publisher does not have to involve a global addressing system where anything can subscribe to anything.  One can do a local system based on messages where one can only send a subscription message to an actor whose address you already have.  I don't know how the OP's linked package does it, but the Subscribe-Notify system in Messenger Library is based on subscription messages.

Technically, the "low-coupling" message techniques are closely related to subscribing, so one could build on that.