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

Added support for topic based exchanges and multiple consumers #3

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

mikery
Copy link

@mikery mikery commented Jun 6, 2011

I needed to use topic-based exchanges, so I removed the hard-coded 'type="direct"' exchange declarations. It will default to "direct" if no exchange_type is specified.

I also added an examples dir with a file showing how to use a topic-based exchange with txamqp to help people get up and running quickly.

topic exchanges can be used.

Due to the way amqp.py declares the exchange in multiple locations,
exchange_type needs to be passed around in quite a few places.

Changed consumer tag and queue name so they are based on the
exchange name and routing key. The previous method of just using
the exchange name meant there could only be one consumer per exchange.
a topic exchange.

Added RabbitMQ spec file to .gitignore.
@pfreixes
Copy link

pfreixes commented Sep 5, 2012

Not just you should give type argument, all params behind exchange declare must be give

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

Successfully merging this pull request may close these issues.

2 participants