XMQ
XMQ are lightweight, self-healing, frictionless messaging Agents that send and receive data using a .Net implementation of the open-source Zero MQ library.
The agents form a resilient network where each object can assume the server role, making it capable of self-healing if one agent disconnects.
They are useful in several scenarios:
Stream within a stream You could have one Data Stream that performs pre-processing and then passes it off to several other Data Streams for further processing - rather than duplicating the pre-processing logic.
Jupyter notebook You could listen for or send data from a Notebook to a Data Stream.
Trigger a Data Stream from an Application Add an action to a Button Block in Application Designer to trigger a Data Stream to send a value to a Data Stream.
Because any Stream Object using these Agents can assume the server role, changing the authentication settings must be performed carefully.
A Stream Object with old or incorrect settings may take the server role and reject connections from ones with correct settings.
Although our examples use manually entered values for simplicity, we recommend always using variables for the authentication settings.
The Listener allows you to subscribe to other XMQ Action Agents for data they have published.
The Action Agent allows you to publish data to other XMQ Agents - and subscribe to topics like the Listener.
Pre-requisites
To facilitate self-healing, linked Agents must connect to a port on the same machine as it is running - i.e. a port on the 127.0.0.1 address.
Current Version
XMQ Listener Release Notes
v1.01, 08 Apr 2024
Fixed concurrent access exception
v1.0, 22 Dec 2023
Initial Release
XMQ Action Agent Release Notes
v1.01, 08 Apr 2024
Fixed concurrent access exception
v1.0, 22 Dec 2023
Initial Release
Last updated