From e603a00ecdd051bd92eee62333c46c7f1b1605a3 Mon Sep 17 00:00:00 2001 From: davidklempfner1 <167742523+davidklempfner1@users.noreply.github.com> Date: Tue, 17 Jun 2025 09:45:07 +1000 Subject: [PATCH] Update at_least_once_delivery.md Fixed typo. --- _docs/at_least_once_delivery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/at_least_once_delivery.md b/_docs/at_least_once_delivery.md index 9816bf8..59c7ede 100644 --- a/_docs/at_least_once_delivery.md +++ b/_docs/at_least_once_delivery.md @@ -16,7 +16,7 @@ In case of failures that lead to message loss or take too long to recover from, Sometimes, message duplicity can be coped with by the application using a [Message-oriented Middleware](/message_oriented_middleware/). Therefore, for scenarios where message duplicates are uncritical, it shall still be ensured that messages are received. ### Solution -For each message retrieved by a receiver an acknowledgement is sent back to the message sender. In case this acknowledgement is not received after a certain time frame, the message is resend. +For each message retrieved by a receiver an acknowledgement is sent back to the message sender. In case this acknowledgement is not received after a certain time frame, the message is resent. ![At-least-once Delivery]({{ "/sketches/at_least_once_delivery_sketch.png" | prepend: site.baseurl }})