As far as I know, zmq doesn't need a broker but subscribers should know the
address of the publisher, if the network increases its complexity with more
publishers you need a broker, that is a proxy on zmq.
If I understand well you need any of them should be able to publish a
change to all of the o
Hi Sven,
Thanks, now I understand better the use of QoS and session ID with a
practical use case.
How do you deal with the lifetime of each "listener" (subscriber) on
each image? I mean, how stable is it?
E.g.
MQTTClient new
open;
subscribeToTopic: '/updates';
runWith: [ :message |
On Thu, Jul 1, 2021 at 3:00 PM Jesus Mari Aguirre
wrote:
>
> As far as I know, zmq doesn't need a broker but subscribers should know the
> address of the publisher, if the network increases its complexity with more
> publishers you need a broker, that is a proxy on zmq.
> If I understand well y
> On 1 Jul 2021, at 20:58, Esteban Maringolo wrote:
>
> Hi Sven,
>
> Thanks, now I understand better the use of QoS and session ID with a
> practical use case.
>
> How do you deal with the lifetime of each "listener" (subscriber) on
> each image? I mean, how stable is it?
>
> E.g.
> MQTTCli
> On 1 Jul 2021, at 21:01, Esteban Maringolo wrote:
>
> On Thu, Jul 1, 2021 at 3:00 PM Jesus Mari Aguirre
> wrote:
>>
>> As far as I know, zmq doesn't need a broker but subscribers should know the
>> address of the publisher, if the network increases its complexity with more
>> publishers
