Hi,
This is not the complete requirements set we need. Sorry for
any inconvenience occurred.
Thank you. Regards.
On Sun, 29 Sep 2019 at 18:25, Isuru Boyagane
wrote:
> Hi,
>
> We are implementing a use case that needs tight at least once delivery.
> Even in the case of failures of nodes, no mes
Hi,
We are implementing a use case that needs tight at least once delivery.
Even in the case of failures of nodes, no messages must be lost.
We are trying to find out the least restrictive configurations that can
give us at least once delivery. Following is what we found.
-
If we use ack