On 02/01/2014 12:13 AM, Justin wrote:
1. I need to be able to support the one-to-many messaging paradigm, but my current setup isn't doing this. Specifically, I have one application publishing commands to a queue with an address like:applicationCommand / applicationName ; { create: always, node:{ type: queue, durable: true }} This command is intended for only a single instance of a single application, however right now it seems only the first instance of that application ever gets this message (first as in, the first one to grab it from the queue). If it isn't the right instance, the command never gets to the right place. I know that I could add additional data to the subjectto avoid this problem, but is we have other scenarios where queue'd data needs to get to multiple receivers. Is this possible somehow? I couldn't find anything in x-declare, but perhaps I missed it.
I don't understand your use case sufficiently. Could you give some more detail/examples of what is happening and how you want it to behave instead?
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
