Hi Lionel,
If I understand your use case correctly, then MQTT has a feature that does
exactly what you're trying to achieve. Retained messages.
"When a workstation connects, I want it to be able to get the most recent
value immediately."
A producer can mark a message as "retain". The broker
> Can the multicast work for a client who is connecting for the first time?
I'm not entirely clear on your question here. Are you talking about using
UDP multicast for server discovery or using a multicast address and/or
queue?
> Will they immediately get the last value?
In a last-value queue
One more question, I've read the documentation several times and plan to
implement soon and test some scenarios. Can the multicast work for a client
who is connecting for the first time? Will they immediately get the last
value?
On 13 August 2017 at 09:10, Justin Bertram
A multicast address is something you configure on the ActiveMQ Artemis
broker. See more details in the documentation [1].
Justin
[1] http://activemq.apache.org/artemis/docs/latest/address-model.html
On Sat, Aug 12, 2017 at 5:36 PM, Lionel van den Berg
wrote:
> I can be
I can be flexible on the protocol. Currently we are using openwire.
For the option of a multicast address, is this an activemq configuration or
network configuration? OK, it's in activemq and there is some
documentation, I'll get to ready. At first glance it seems there are some
limitations, but
What client protocol/API are you going to be using?
I think you could accomplish what you're after by using a multicast address
with multiple last-value queues which represent all your workstations. How
you access those will depend on what protocol/API you decide to use.
Justin
On Fri, Aug
Hi,
I'm currently using activemq and now looking into Artemis. One of the
interest features I see is the is the last-value queue option. However what
I want to use it for is for regularly updating data and not so regular
updating data where the last value is always the only interesting value,
but