This sounds like an architecturally wrong fit for a dispatch router and
like a better fit for a message broker. The router has no place to store
messages and it is not an endpoint capable of taking ownership of messages.

See docs/books/user-guide/theory_of_operation.adoc, section Message Routing/
Routing Patterns. Acknowledged deliveries are performed only with Anycast
distribution and Multicast deliveries are unreliable.

----- Original Message -----
> From: "VERMEULEN Olivier" <[email protected]>
> To: [email protected]
> Sent: Tuesday, November 13, 2018 8:58:55 AM
> Subject: RE: [Dispatch Router] multicast distribution
> 
> I guess yes, all the active subscribers when the router receives the message.
> If the message is not successfully acked by all of them, then yes the message
> is requeued and sent again to all active subscribers.
> If one of the subscribers disconnects in the middle of the process I would
> say we are back to the previous case and the message is resent to all active
> subscribers.
> We don't really mind receiving the message twice in some corner cases.
> 
> Olivier
> 
> -----Original Message-----
> From: Gordon Sim <[email protected]>
> Sent: lundi 12 novembre 2018 21:46
> To: [email protected]
> Subject: Re: [Dispatch Router] multicast distribution
> 
> On 12/11/18 19:32, VERMEULEN Olivier wrote:
> > when all receivers acknowledge it
> 
> How is the set of 'all' receivers defined? All those active at the time the
> message is received by the first router? (What if one of them had been
> disconnected just before that message?)
> 
> If a message is not successfully acked, would it be requeued and replayed to
> all subscribers?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] For additional
> commands, e-mail: [email protected]
> 
> ******************************* This e-mail contains information for the
> intended recipient only. It may contain proprietary material or confidential
> information. If you are not the intended recipient you are not authorized to
> distribute, copy or use this e-mail or any attachment to it. Murex cannot
> guarantee that it is virus free and accepts no responsibility for any loss
> or damage arising from its use. If you have received this e-mail in error
> please notify immediately the sender and delete the original email received,
> any attachments and all copies from your system.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to