-
15. Re: Reliable delivery
"timfox" wrote:
"vc123" wrote:
1. I will, but we do not want DUPS ;)
Well you won't get reliable (once and only) delivery using AUTO_ACKNOWLEDGE either.
AUTO_ACK = *at most once*
Right, I won't, but just possibly losing some messages still better than risking losing a message *and* possibly getting duplicates (we can afford losing some messages and then requesting retransmission through a persistent channel/queue). -
16. Re: Reliable delivery
Right, I won't, but just possibly losing some messages still better than risking losing a message *and* possibly getting duplicates (we can afford losing some messages and then requesting retransmission through a persistent channel/queue).
Or you could make your app idempotent and handle the duplicates yourself. -
17. Re: Reliable delivery
You can't lose messages with DUPS_OK, but there is a possibility of duplicates if the system fails and recovers.
As Andy says, you can then implement duplicate detection and effectively then get once and only once delivery.