-
Limiting the number of QoS 1 and 2 publications that can be processed simultaneously by both server and client.
-
Formalize the request/response pattern within MQTT and provide the Response Topic and Correlation Data properties to allow response messages to be routed back to the publisher of a request. Also, add …
-
Allow a numeric subscription identifier to be specified on a SUBSCRIBE, and returned on the message when it is delivered. This allows the Client to determine which subscription or subscriptions caused…
-
Provide subscription options primarily defined to allow for message bridge applications. These include an option to not send messages originating on this Client (noLocal), and options for handling ret…
-
Allow an expiry interval to be set when a message is published.
-
On "client_test5.py Test.test_basic", client talked PUBREL started by 0x64, while standard requests 0x62. Seemed malformed.
-
Add User Properties to PUBLISH and CONNECT, and to all packets with a Reason Code. User properties on PUBLISH are included with the message and are defined by the Client applications. The user propert…
-
Allow the Server to specify the value it wishes the Client to use as a keep alive. This allows the Server to set a maximum allowed keepalive and still have the Client honor it.
-
Allow the Client and Server to independently specify the maximum packet size they support. It is an error for the session partner to send a larger packet.
-
In cases where the ClientID is assigned by the Server, return the assigned ClientID. This also lifts the restriction that Server assigned ClientIDs can only be used with Clean Session=1 connections.