Thomas Strauß created CAMEL-25030:
-------------------------------------
Summary: Supply a MQTT 3.1.1 component
Key: CAMEL-25030
URL: https://issues.apache.org/jira/browse/CAMEL-25030
Project: Camel
Issue Type: New Feature
Components: camel-mqtt
Affects Versions: 4.22.1
Reporter: Thomas Strauß
camel-paho supplies currently the mqtt3.1.1 implementation but is deprecated in
4.22-LTS. Since other MQTT implementations only support mqtt 5+, camel looses
connectivity to the mqtt3.1.1 standard.
mqtt.org still supports mqtt3.1.1 as a living release and actually suggests it
for wide compatibility. Many non-mqtt brokers support only 3.1.1 as an industry
standard alternative to the proprietary protocol. In my usecase this is
nats.io, but others can be found.
Using a proprietary protocol means to enforce interface partners to use the
proprietary library and also enforces possible client updates when the
technology is updated. Using an industry standard on your external interfaces
links you to the industry standard life-cycle which is an entirely different
thing.
Long story short: The camel stack should offer a new implementation on
mqtt3.1.1 to keep connected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
