Yes we already thought of that as a fallback plan. I guess we will go for this approach. Thanks Gordon for your time.
Olivier -----Original Message----- From: Gordon Sim <[email protected]> Sent: mercredi 14 novembre 2018 13:15 To: [email protected] Subject: Re: [Dispatch Router] multicast distribution On 14/11/18 11:59, VERMEULEN Olivier wrote: > No if the subscriber is still down the message should also be resent. > So you're right it's not simply the active subscribers, it would be all the > subscribers that were connected to the dispatch-router at some point and that > were not explicitly closed. > Actually it's not even limited to the dispatch-router that received the > message, we should also consider all the dispatch-routers inter-connected > with it. I think explicit management of the subscriptions might be a better way to approach the problem. For each subscriber, set up a unique subscription queue on each broker of relevance, and have a link from the broker sending messages out through an anycast address on the router network that matches the subscription identifier. Then the subscribe can simply attach a receiver on that identifier to the router network and that will trigger the flow of messages from all queues which can then be acknowledged end-to-end. --------------------------------------------------------------------- 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.
