You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EventSubscriber and EventPublisher are the easiest ways to get your b-rabbit messenger service up and running. Currently, it is only utilizing a portion of the low-level features that rabbitpy and RabbitMQ provides.
If you would like to contribute to the project, adding these features to the mentioned classes would be a great way to help brabbit become a more dynamic solution to AMPQ with multithreading support.
Here are some examples of features that could be implemented:
The EventSubscriber and EventPublisher are the easiest ways to get your b-rabbit messenger service up and running. Currently, it is only utilizing a portion of the low-level features that rabbitpy and RabbitMQ provides.
If you would like to contribute to the project, adding these features to the mentioned classes would be a great way to help brabbit become a more dynamic solution to AMPQ with multithreading support.
Here are some examples of features that could be implemented:
Channel parameters, such as maximum_frame_size, id, exception queue, etc.
https://rabbitpy.readthedocs.io/en/latest/api/channel.html
Queue parameters, specifically for the EventSubscriber class, such as auto_delete, message_ttl, etc.
https://rabbitpy.readthedocs.io/en/latest/api/queue.html
Add methods to easily retrieve information from connection in BRabbit object.
Any other creative suggestions that allow this high-level API to provide low-level functionality!
The text was updated successfully, but these errors were encountered: