I believe the term here is application level heartbeats.

It should also be supported that clients can heartbeat to server. It
is not always that all clients want similar heartbeat timeouts.

On Mon, Feb 13, 2017 at 4:07 PM, Michal Vyskocil
<[email protected]> wrote:
> Hi,
>
> You can take inspiration from malamute broker
> https://github.com/zeromq/malamute
>
> There clients pings server regularly. The same does MQTT (just it's a
> server, who pings clients).
>
> Sadly malamute is vulnerable to the same problem, that received service
> request may get lost. Solution would be to let client to send a request
> again after timeout, however wasn't yet implemented.
>
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev



-- 
Studying for the Turing test
_______________________________________________
zeromq-dev mailing list
[email protected]
https://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to