WHAT?
Idea behind this is, we can create some sort of plugin system, so users can create their own mechanism for dealing with messages from RabbitMQ.
WHY?
Right now, we support 2 main ways of dealing with messages, one-by-one and multi-message mechanism. This is hardcoded into code, so we need to create some crazy IFs for this to get it working. Idea of this ticket is, to provide easy plugin/resolver type of class, that will be like middleware, so users can do big magic and this library will support them in their work.
One example, in v11 we added auto DLX queues, so messages can be redelivered automaticly, but we can do this only in specific time frame, but if we want some kind of auto-repeat for several times or with increasing time, there is no easy way of doing this. With plugin mechanism, we can modify consumer in way, on reject it will do dlx stuff, and app does not need to know about this.
WHAT?
Idea behind this is, we can create some sort of plugin system, so users can create their own mechanism for dealing with messages from RabbitMQ.
WHY?
Right now, we support 2 main ways of dealing with messages, one-by-one and multi-message mechanism. This is hardcoded into code, so we need to create some crazy IFs for this to get it working. Idea of this ticket is, to provide easy plugin/resolver type of class, that will be like middleware, so users can do big magic and this library will support them in their work.
One example, in v11 we added auto DLX queues, so messages can be redelivered automaticly, but we can do this only in specific time frame, but if we want some kind of auto-repeat for several times or with increasing time, there is no easy way of doing this. With plugin mechanism, we can modify consumer in way, on reject it will do dlx stuff, and app does not need to know about this.