MQTT::V5::Connect
Inherits MQTT::Header / BinData / Reference / Object
MQTT-3.1. Same shape as 3.1.1 with a property section after the keep alive, and a second property section in front of the will topic
Constants
MQTT-3.1. Same shape as 3.1.1 with a property section after the keep alive, and a second property section in front of the will topic
MQTT-3.1. Same shape as 3.1.1 with a property section after the keep alive, and a second property section in front of the will topic
MQTT-3.1. Same shape as 3.1.1 with a property section after the keep alive, and a second property section in front of the will topic
MQTT-3.1. Same shape as 3.1.1 with a property section after the keep alive, and a second property section in front of the will topic
MQTT-3.1. Same shape as 3.1.1 with a property section after the keep alive, and a second property section in front of the will topic
MQTT-3.1. Same shape as 3.1.1 with a property section after the keep alive, and a second property section in front of the will topic
Class methods
MQTT-3.1. Same shape as 3.1.1 with a property section after the keep alive, and a second property section in front of the will topic
Instance methods
A group or bit_field captures the endianness at its declaration point, so
declaring endian after one would silently leave it system-endian. Fail loudly.
How long the broker keeps the session after we disconnect. 5.0 uses this instead of 3.1.1's clean session flag alone
MQTT-3.1.3.3, the will payload is binary data rather than a string
MQTT-3.1.3.3, the will payload is binary data rather than a string
the will has its own property section, and it precedes the will topic
the will has its own property section, and it precedes the will topic