Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reply_to requires queue name, but used as routing key #1

Open
orlade opened this issue Aug 19, 2014 · 0 comments
Open

reply_to requires queue name, but used as routing key #1

orlade opened this issue Aug 19, 2014 · 0 comments

Comments

@orlade
Copy link

orlade commented Aug 19, 2014

TAMQOutputTransportFactory uses msg.properties['reply_to'] as a routing key for the response message, however TAMQTransport (used on the client side) populates the reply_to property with the queue kwarg. queue is required to be the name of a queue, not a routing key, and thus this pair of transports will only work if the response queue is bound to a key which is the name of a queue (typically itself).

In other words, it assumes a default exchange type, not a direct exchange, but this isn't made particularly clear (TAMQFactory even declares direct exchanges, but binds the queues to their names like a default exchange).

So this is really a request to support direct exchanges. I may add this later if it proves useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant