Issue #6938 has been updated by R.I. Pienaar.
To clarify, my preference would be ActiveMQ because this kind of feature is only going to make a big difference on big sites who would cluster their middleware and scale horizontally, or on sites with high latency between various DCs. Since RabbitMQ doesnt really do well on WAN links it's mostly a waste of time doing this for Rabbit based sites. ---------------------------------------- Feature #6938: Clients should be able to specify a specific reply destination in requests https://projects.puppetlabs.com/issues/6938 Author: R.I. Pienaar Status: Accepted Priority: Normal Assignee: R.I. Pienaar Category: Core Target version: Keywords: Branch: Affected mCollective version: At present replies simply go to <collectivename>.<agent>.reply this is not great in cases where many consumers are using mcollective and you have 1000s of machines, users will get each others replies and simply ignore them. We've not used temp topic or unique topics due to bugs in ActiveMQ but these are slowly going away so should start supporting custom reply destinations. This should be a configurable setting that sets it for the whole client but individual requests should just be able to add an optional member int he request hash declaring a response destination. If none is supplied it should work in a backward compat way and this should be the default behavior. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
