Peter Silva

in case it is helpful, the feature that most interests me is shared queues. with AMQP 0.9 you just have multiple processes connect to the same queue to do sharing....

No need for new features on the rabbit side. The existing sharing of queues (has been there last ten years or so) is fine... I just have multiple subscribers connect...

What would be really cool for v5 support: -- map each topic exchange to the root of mqtt topic tree. -- prepend with $share/queue_name/exchange/ .... rest of the topics. If...

fwiw... I use this mapping here: https://github.com/MetPX/sarracenia/tree/v03_wip/sarracenia/moth There are MQTT and AMQP sub-classes of the "Messages Organized by Topic Header" I use mosquitto for the MQTT stuff, because the rabbitmq...

The build travis failures are in areas of the code with nothing to do with my changes. Pre-existing issue. I think I have signed the appropriate contributor agreement.

@BBBSnowball about 1. OK I can clarify... Yes the language should be firmer... something like "the application must explicitly call the ack function for each message received." I would prefer...

@ralight I re-signed the ECA, and it seems happy now. I started looking at how to do what you are asking for. The original patch was pretty straight-forward. I just...

oh... and thanks for reading the patch! appreciated!

After prodding from the two of you, I just looked hard and found section 4.6 message ordering... so that means if the application returns acks out of order, they need...

I´m fine with the suggestions and can look at implementing what is requested. People should just appreciate that the small fix I did was really simple, and didn´t require nearly...