-
Notifications
You must be signed in to change notification settings - Fork 43
Support for Fanout exchanges #34
Comments
Hi @c-brooks I'm not working with AMQP anymore. Also, AFAIK people at NeowayLabs don't use RabbitMQ anymore... I support the forking of this library. If someone implements this feature or is actively fixing bugs on his own fork, let me know and I can add a notice in the readme redirecting users to a most up to date repository. Maybe we can even transfer this repository ownership to someone else (but I don't know if that's possible). @matheusvill What do you think? Thank you for your kind words. |
@satta I just find out you maintain a Debian/Ubuntu package of this library. Would you like to maintain this project as well? There are other forks that implement missing features and/or fix bugs, then what's needed is just review and ensure tests pass, and so on. It's completely fine if you can't or don't want to. |
Hi Tiago, thanks for your consideration. However, I sadly must admit that at them moment my time is too limited to be able to fully adopt this project, sorry. I hope you can find someone with more spare time... |
Hi @satta, It's completely fine. @c-brooks About the fanout exchange: https://www.rabbitmq.com/resources/specs/amqp0-9-1.pdf It's much simpler than the |
We have code that uses the
fanout
exchange type, which works fine against a real RabbitMQ server but fails our test suite against awabbit
fake server with the error message:I searched the wabbit codebase and couldn't find any mention of the
fanout
exchange type. Are there any plans on implementing this ?Thanks, love the library. Keep up the good work 👍
The text was updated successfully, but these errors were encountered: