Support for mqtt-v5

[Nasry Al-Haddad]

Hello,

Are there any plans to update the MQTT adapter to support mqtt-v5 in the coming months?

http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.html

Regards,

Nasry

[Michael Klishin]

We'd like to support MQTT v5 but haven't checked out the difference with v3.1 and there's a good chance

the version is not backwards compatible. So there is no ETA and there's a good chance that this

will ship in RabbitMQ 3.8 the earliest.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Peter Silva]

Was looking over MQTTv5...  some parts that were interesting for me:

*User Properties* == AMQP headers, but 64Kb instead of 255b.

*Shared subscriptions* == multiple subscribers using the same queue.

that will be useful when it arrives.

On Thursday, July 19, 2018 at 10:28:59 AM UTC-4, Michael Klishin wrote:

We'd like to support MQTT v5 but haven't checked out the difference with v3.1 and there's a good chance

the version is not backwards compatible. So there is no ETA and there's a good chance that this

will ship in RabbitMQ 3.8 the earliest.

On Thu, Jul 19, 2018 at 10:24 AM, Nasry Al-Haddad <nasry....@elementn.com> wrote:

Hello,

Are there any plans to update the MQTT adapter to support mqtt-v5 in the coming months?

http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.html

Regards,

Nasry

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michael Klishin]

I don't know if 64 kB headers is such a good idea. You can put any metadata into message payload today, with incredibly

high message payload limits (512 MiB in future RabbitMQ versions, 2 GiB today), with any protocol.

You can have competing consumers on a queue today, with any protocol. My guess is that with shared subscriptions

each subscriber can consume a copy of the message.

The earliest release for which MQTTv5 would be considered is 3.9 (no ETA promises), in part because features such as

shared subscription would require significant changes to certain internal APIs first since that's not how the protocols we support

today work.