develop
master
fixes
release/2.0
release/1.6
dynamic-bridge
release/1.5
debian
debian-mosquitto
v2.0.15
v2.0.14
v2.0.13
v2.0.12
v2.0.11
v1.6.15
v2.0.10
v2.0.9
v1.6.14
v1.5.11
v2.0.8
v2.0.7
v1.6.13
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.5.10
v1.6.12
v1.6.11
v1.6.10
v1.6.9
v1.6.8
v1.6.7
v1.6.6
v1.5.9
v1.6.5
v1.6.4
v1.6.3
v1.6.2
v1.6.1
v1.6
v1.5.8
v1.5.7
v1.5.6
v1.5.5
v1.5.4
v1.5.3
v1.5.2
v1.5.1
v1.5
v1.4.15
v1.4.14
v1.4.13
v1.4.12
v1.4.11
v1.4.10
v1.4.9
v1.4.8
v1.4.7
v1.4.6
v1.4.5
v1.4.4
v1.4.3
v1.4.2
v1.4.1
v1.3.2-not-blessed
v1.3.3-not-blessed
v1.3.4-not-blessed
v1.3.5-not-blessed
v1.4
${ noResults }
1 Commits (4b97a90ef91e2dbbab5a754ba2f9ac4cf85288fe)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Roger A. Light
|
326292681a |
Add maximum-qos support to broker and client.
This comes in the form of: * Per listener maximum_qos option, which can be in the range 0-2. * Changes to mosquitto_publish*() to return MOSQ_ERR_QOS_NOT_SUPPORTED if attempting to publish with a higher QoS than supported. * Bridges will downgrade messages to match the maximum QoS. More tests on the broker side (specifically bridges) are required. This needs bridge support for MQTT 5 first. |
7 years ago |