Maps to Disabled. This keeps the client from being broken (by default) if the broker topic aliasing implementation has a problem.
Outbound aliasing is the user's responsibility. Client will cache and use previously-established aliases if they fall within the negotiated limits of the connection.
The user must still always submit a full topic in their publishes because disconnections disrupt topic alias mappings unpredictably. The client will properly use a requested alias when the most-recently-seen binding for a topic alias value matches the alias and topic in the publish packet.
(Recommended) The client will use an LRU cache to drive alias usage.
Manually setting a topic alias will be ignored (the LRU cache is authoritative)
Completely disable outbound topic aliasing.
Generated using TypeDoc
An enumeration that controls how the client applies topic aliasing to outbound publish packets.
Topic alias behavior is described in https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901113