An MQTT session holds the state of an MQTT client (that is, it contains a client’s QoS 0 and QoS 1 topic filter sets and any undelivered QoS 1 messages). The MQTT client connection also requires an MQTT session on the server.Īn MQTT session object is a virtual representation of an MQTT client connection that exists as a managed object on an event broker. MQTT SessionsĪn MQTT client connecs to a specific Message VPN on an event broker, using a dedicated MQTT port configured for that Message VPN. It'll take you on a tour of the PubSub+ event broker's messaging components, and explain at a high level how they make data move from producers to the broker, and from the broker to consumers, with MQTT.
If you haven't used MQTT and Solace PubSub+ together before, you might want to look at the MQTT section of the Overview: How Apps Interact with PubSub+ Messaging Components page.
It is strongly recommended that network architects and programmers review this document. There are annotated versions of the specifications ( Solace MQTT Version 3.1.1 Protocol Conformance Specification and Solace MQTT Version 5.0 Protocol Conformance Specification) that highlight any deviations, limitations, or choices that have been made in the "SHOULD" and "MAY" clauses of the protocol specifications for the Solace implementation.Solace's implementation of MQTT complies with OASIS Standards MQTT v3.1.1 and MQTT v5.0.