diff --git a/docs/MQTTAsync/html/_h_t_t_p_proxies.html b/docs/MQTTAsync/html/_h_t_t_p_proxies.html index 5bf9475c..5dd442eb 100644 --- a/docs/MQTTAsync/html/_h_t_t_p_proxies.html +++ b/docs/MQTTAsync/html/_h_t_t_p_proxies.html @@ -3,15 +3,13 @@
- +The use of HTTP proxies can be controlled by environment variables or API calls.
@@ -96,7 +83,7 @@ $(function(){ initResizable(false); });Go to the source code of this file.
+Data Structuresstruct | MQTTAsync_init_options | | struct | MQTTAsync_message | | struct | MQTTAsync_connectData | | struct | MQTTAsync_failureData | | struct | MQTTAsync_failureData5 | | struct | MQTTAsync_successData | | struct | MQTTAsync_successData5 | | struct | MQTTAsync_responseOptions | | struct | MQTTAsync_createOptions | | struct | MQTTAsync_willOptions | | struct | MQTTAsync_SSLOptions | | struct | MQTTAsync_nameValue | | struct | MQTTAsync_connectOptions | | struct | MQTTAsync_disconnectOptions | | struct | MQTTAsync_init_options | struct | MQTTAsync_connectData | struct | MQTTAsync_failureData | struct | MQTTAsync_failureData5 | struct | MQTTAsync_successData | struct | MQTTAsync_successData5 | struct | MQTTAsync_responseOptions | struct | MQTTAsync_createOptions | struct | MQTTAsync_willOptions | struct | MQTTAsync_SSLOptions | struct | MQTTAsync_nameValue | struct | MQTTAsync_connectOptions | | struct | MQTTAsync_disconnectOptions | |||||||||||||||||
+Typedefs | | | | | | | | | | | | | | | | ||||||||||||||||||||||||||||||||||||||||||||||||
+Enumerations | |||||
Return code: protocol prefix in serverURI should be:
The TLS enabled prefixes (ssl, mqtts, wss) are only valid if the TLS version of the library is linked with.
+The TLS enabled prefixes (ssl, tls, mqtts, wss) are only valid if the TLS version of the library is linked with.
+Data Structuresstruct | MQTTClient_persistence | | A structure containing the function pointers to a persistence implementation and the context or state that will be shared across all the persistence functions. More... | | struct | MQTTClient_persistence | |||||
+Macros | | | | | |||||||||||||||
+Typedefstypedef int(* | Persistence_open) (void **handle, const char *clientID, const char *serverURI, void *context) | | typedef int(* | Persistence_close) (void *handle) | | typedef int(* | Persistence_put) (void *handle, char *key, int bufcount, char *buffers[], int buflens[]) | | typedef int(* | Persistence_get) (void *handle, char *key, char **buffer, int *buflen) | | typedef int(* | Persistence_remove) (void *handle, char *key) | | typedef int(* | Persistence_keys) (void *handle, char ***keys, int *nkeys) | | typedef int(* | Persistence_clear) (void *handle) | | typedef int(* | Persistence_containskey) (void *handle, char *key) | | | | | |||||||||||||||||||||||||||||||||
This structure represents a persistent data store, used to store outbound and inbound messages, in order to achieve reliable messaging.
The MQTT Client persists QoS1 and QoS2 messages in order to meet the assurances of delivery associated with these Quality of service levels. The messages are saved in persistent storage The type and context of the persistence implementation are specified when the MQTT client is created (see MQTTClient_create()). The default persistence type (MQTTCLIENT_PERSISTENCE_DEFAULT) uses a file system-based persistence mechanism. The persistence_context argument passed to MQTTClient_create() when using the default peristence is a string representing the location of the persistence directory. If the context argument is NULL, the working directory will be used.
To use memory-based persistence, an application passes MQTTCLIENT_PERSISTENCE_NONE as the persistence_type to MQTTClient_create(). This can lead to message loss in certain situations, but can be appropriate in some cases (see Quality of service).
Client applications can provide their own persistence mechanism by passing MQTTCLIENT_PERSISTENCE_USER as the persistence_type. To implement a custom persistence mechanism, the application must pass an initialized MQTTClient_persistence structure as the persistence_context argument to MQTTClient_create().
If the functions defined return an MQTTCLIENT_PERSISTENCE_ERROR then the state of the persisted data should remain as it was prior to the function being called. For example, if Persistence_put() returns MQTTCLIENT_PERSISTENCE_ERROR, then it is assumed tha tthe persistent store does not contain the data that was passed to the function. Similarly, if Persistence_remove() returns MQTTCLIENT_PERSISTENCE_ERROR then it is assumed that the data to be removed is still held in the persistent store.
It is up to the persistence implementation to log any error information that may be required to diagnose a persistence mechanism failure.
-Go to the source code of this file.
+Data Structuresstruct | MQTTLenString | | struct | MQTTProperty | | struct | MQTTProperties | | struct | MQTTLenString | struct | MQTTProperty | | struct | MQTTProperties | ||||||
+Macros | | | |||||||||
+Typedefs | | ||||||
+Enumerations | |||||
| enum | MQTTPropertyTypes { MQTTPROPERTY_TYPE_BYTE , MQTTPROPERTY_TYPE_TWO_BYTE_INTEGER @@ -171,40 +151,25 @@ Enumerations | ||||
Go to the source code of this file.
+Enumerations | |||||
+Functions | | ||||||
+Data Structuresstruct | MQTTSubscribe_options | | | struct | MQTTSubscribe_options | ||||
+Macros | | ||||||
+Typedefs | | ||||||
The client application runs on several threads. Processing of handshaking and maintaining the network connection is performed in the background. This API is thread safe: functions may be called by multiple application threads. Notifications of status and message reception are provided to the client application using callbacks registered with the library by the call to MQTTAsync_setCallbacks() (see MQTTAsync_messageArrived(), MQTTAsync_connectionLost() and MQTTAsync_deliveryComplete()). In addition, some functions allow success and failure callbacks to be set for individual requests, in the MQTTAsync_responseOptions structure. Applications can be written as a chain of callback functions.
@@ -93,7 +80,7 @@ $(function(){ initResizable(false); });The ability for the client library to reconnect automatically in the event of a connection failure was added in 1.1. The connection lost callback allows a flexible response to the loss of a connection, so almost any behaviour can be implemented in that way. Automatic reconnect does have the advantage of being a little simpler to use.
@@ -95,7 +82,7 @@ $(function(){ initResizable(false); });Any function from this API may be used within a callback. It is not advisable to use MQTTAsync_waitForCompletion within a callback, however, as it is the only API call that may take some time to complete, which may cause unpredictable behaviour. All the other API calls are intended to complete quickly, starting a request in the background, with success or failure notified by other callbacks.
@@ -94,7 +81,7 @@ $(function(){ initResizable(false); });| MQTTAsync.h | |
| MQTTClientPersistence.h | This structure represents a persistent data store, used to store outbound and inbound messages, in order to achieve reliable messaging |
| MQTTProperties.h | |
| MQTTReasonCodes.h | |
| MQTTSubscribeOpts.h | |
| MQTTAsync.h | |
| MQTTClientPersistence.h | This structure represents a persistent data store, used to store outbound and inbound messages, in order to achieve reliable messaging |
| MQTTProperties.h | |
| MQTTReasonCodes.h | |
| MQTTSubscribeOpts.h |
An Asynchronous MQTT client library for C.
© Copyright 2009, 2025 IBM Corp., Ian Craggs and others.
-Version 1.3.14
+Version 1.3.15
An MQTT client application connects to MQTT-capable servers. A typical client is responsible for collecting information from a telemetry device and publishing the information to the server. It can also subscribe to topics, receive messages, and use this information to control the telemetry device.
MQTT clients implement the published MQTT v3 protocol. You can write your own API to the MQTT protocol using the programming language and platform of your choice. This can be time-consuming and error-prone.
To simplify writing MQTT client applications, this library encapsulates the MQTT v3 protocol for you. Using this library enables a fully functional MQTT client application to be written in a few lines of code. The information presented here documents the API provided by the Asynchronous MQTT Client library for C.
@@ -146,7 +133,7 @@ Free any memory being used by the clientThis feature was not originally available because with persistence enabled, messages could be stored locally without ever knowing if they could be sent. The client application could have created the client with an erroneous broker address or port for instance.
@@ -95,7 +82,7 @@ $(function(){ initResizable(false); });The MQTT protocol provides three qualities of service for delivering messages between clients and servers: "at most once", "at least once" and "exactly once".
@@ -100,7 +87,7 @@ $(function(){ initResizable(false); });#include <MQTTAsync.h>
+Data Fields | | | | | | | | | | | | | | | | | | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MQTTAsync_sslProperties defines the settings to establish an SSL/TLS connection using the OpenSSL library. It covers the following scenarios:
#include <MQTTAsync.h>
+Data Fields | | } | binarypwd | | ||||||||||||||||||||||||||||||||||||
The connect options that can be updated before an automatic reconnect.
-#include <MQTTAsync.h>
+Data Fields | | | | | | | | | | | | | | | | | | | } | binarypwd | | | | | | | | | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MQTTAsync_connectOptions defines several settings that control the way the client connects to an MQTT server.
Suitable default values are set in the following initializers:
#include <MQTTAsync.h>
+Data Fields | | | | | | | | | | ||||||||||||||||||||||||||||||
Options for the MQTTAsync_createWithOptions call
-Whether the MQTT version is 3.1, 3.1.1, or 5. To use V5, this must be set. MQTT V5 has to be chosen here, because during the create call the message persistence is initialized, and we want to know whether the format of any persisted messages is appropriate for the MQTT version we are going to connect with. Selecting 3.1 or 3.1.1 and attempting to read 5.0 persisted messages will result in an error on create.
-
Whether the MQTT version is 3.1, 3.1.1, or 5. To use V5, this must be set. MQTT V5 has to be chosen here, because during the create call the message persistence is initialized, and we want to know whether the format of any persisted messages is appropriate for the MQTT version we are going to connect with. Selecting 3.1 or 3.1.1 and attempting to read 5.0 persisted messages will result in an error on create.
#include <MQTTAsync.h>
+Data Fields | | | | | | | | | | | |||||||||||||||||||||||||||||||||
Options for the MQTTAsync_disconnect call
-#include <MQTTAsync.h>
+Data Fields | | | | ||||||||||||
The data returned on completion of an unsuccessful API call in the response callback onFailure.
-#include <MQTTAsync.h>
+Data Fields | | | | | | | | | |||||||||||||||||||||||||||
The data returned on completion of an unsuccessful API call in the response callback onFailure.
-#include <MQTTAsync.h>
+Data Fields | | | | ||||||||||||
Initialization options
-#include <MQTTAsync.h>
+Data Fields | | | | | | | | | | ||||||||||||||||||||||||||||||
A structure representing the payload and attributes of an MQTT message. The message topic is not part of this structure (see MQTTAsync_publishMessage(), MQTTAsync_publish(), MQTTAsync_receive(), MQTTAsync_freeMessage() and MQTTAsync_messageArrived()).
-#include <MQTTAsync.h>
+Data Fields | | | |||||||||
Utility structure where name/value pairs are needed
-#include <MQTTAsync.h>
+Data Fields | | | | | | | | | | | | | |||||||||||||||||||||||||||||||||||||||
Structure to define call options. For MQTT 5.0 there is input data as well as that describing the response method. So there is now also a synonym MQTTAsync_callOptions to better reflect the use. This responseOptions name is kept for backward compatibility.
-#include <MQTTAsync.h>
+Data Fields} | alt | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The data returned on completion of a successful API call in the response callback onSuccess.
-#include <MQTTAsync.h>
+Data Fields | | | | } | alt | | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The data returned on completion of a successful API call in the response callback onSuccess.
-#include <MQTTAsync.h>
+Data Fields | | | | | } | payload | | |||||||||||||||||||||||||||||||||||||||||||||
MQTTAsync_willOptions defines the MQTT "Last Will and Testament" (LWT) settings for the client. In the event that a client unexpectedly loses its connection to the server, the server publishes the LWT message to the LWT topic on behalf of the client. This allows other clients (subscribed to the LWT topic) to be made aware that the client has disconnected. To enable the LWT function for a specific client, a valid pointer to an MQTTAsync_willOptions structure is passed in the MQTTAsync_connectOptions structure used in the MQTTAsync_connect() call that connects the client to the server. The pointer to MQTTAsync_willOptions can be set to NULL if the LWT function is not required.
-#include <MQTTClientPersistence.h>
+Data Fields | | | | | | | | | | ||||||||||||||||||||||||||||||
A structure containing the function pointers to a persistence implementation and the context or state that will be shared across all the persistence functions.
-#include <MQTTProperties.h>
+Data Fields | | | |||||||||
The data for a length delimited string
-#include <MQTTProperties.h>
+Data Fields | | | | | |||||||||||||||
MQTT version 5 property list
-#include <MQTTProperties.h>
+Data Fields} | value | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Structure to hold an MQTT version 5 property of any type
-#include <MQTTSubscribeOpts.h>
+Data Fields | | | | | | ||||||||||||||||||
The MQTT V5 subscribe options, apart from QoS which existed before V5.
-Runtime tracing can be controlled by environment variables or API calls.
@@ -162,7 +149,7 @@ $(function(){ initResizable(false); });Every MQTT message includes a topic that classifies it. MQTT servers use topics to determine which subscribers should receive messages published to the server.
@@ -103,7 +90,7 @@ A '+' character represents a single level of the hierarchy and is used between dThe use of HTTP proxies can be controlled by environment variables or API calls.
@@ -96,7 +83,7 @@ $(function(){ initResizable(false); });Go to the source code of this file.
+Data Structuresstruct | MQTTClient_init_options | | struct | MQTTClient_message | | struct | MQTTClient_createOptions | | struct | MQTTClient_willOptions | | struct | MQTTClient_SSLOptions | | struct | MQTTClient_nameValue | | struct | MQTTClient_connectOptions | | struct | MQTTResponse | | struct | MQTTClient_init_options | struct | MQTTClient_createOptions | struct | MQTTClient_willOptions | struct | MQTTClient_SSLOptions | struct | MQTTClient_nameValue | struct | MQTTClient_connectOptions | | struct | MQTTResponse | |||||||||||
+Typedefs | | | | | | | | | | | |||||||||||||||||||||||||||||||||
+Enumerations | |||||
Return code: protocol prefix in serverURI should be:
+Data Structuresstruct | MQTTClient_persistence | | A structure containing the function pointers to a persistence implementation and the context or state that will be shared across all the persistence functions. More... | | struct | MQTTClient_persistence | |||||
+Macros | | | | | |||||||||||||||
+Typedefstypedef int(* | Persistence_open) (void **handle, const char *clientID, const char *serverURI, void *context) | | typedef int(* | Persistence_close) (void *handle) | | typedef int(* | Persistence_put) (void *handle, char *key, int bufcount, char *buffers[], int buflens[]) | | typedef int(* | Persistence_get) (void *handle, char *key, char **buffer, int *buflen) | | typedef int(* | Persistence_remove) (void *handle, char *key) | | typedef int(* | Persistence_keys) (void *handle, char ***keys, int *nkeys) | | typedef int(* | Persistence_clear) (void *handle) | | typedef int(* | Persistence_containskey) (void *handle, char *key) | | | | | |||||||||||||||||||||||||||||||||
This structure represents a persistent data store, used to store outbound and inbound messages, in order to achieve reliable messaging.
The MQTT Client persists QoS1 and QoS2 messages in order to meet the assurances of delivery associated with these Quality of service levels. The messages are saved in persistent storage The type and context of the persistence implementation are specified when the MQTT client is created (see MQTTClient_create()). The default persistence type (MQTTCLIENT_PERSISTENCE_DEFAULT) uses a file system-based persistence mechanism. The persistence_context argument passed to MQTTClient_create() when using the default peristence is a string representing the location of the persistence directory. If the context argument is NULL, the working directory will be used.
To use memory-based persistence, an application passes MQTTCLIENT_PERSISTENCE_NONE as the persistence_type to MQTTClient_create(). This can lead to message loss in certain situations, but can be appropriate in some cases (see Quality of service).
Client applications can provide their own persistence mechanism by passing MQTTCLIENT_PERSISTENCE_USER as the persistence_type. To implement a custom persistence mechanism, the application must pass an initialized MQTTClient_persistence structure as the persistence_context argument to MQTTClient_create().
If the functions defined return an MQTTCLIENT_PERSISTENCE_ERROR then the state of the persisted data should remain as it was prior to the function being called. For example, if Persistence_put() returns MQTTCLIENT_PERSISTENCE_ERROR, then it is assumed tha tthe persistent store does not contain the data that was passed to the function. Similarly, if Persistence_remove() returns MQTTCLIENT_PERSISTENCE_ERROR then it is assumed that the data to be removed is still held in the persistent store.
It is up to the persistence implementation to log any error information that may be required to diagnose a persistence mechanism failure.
-Go to the source code of this file.
+Data Structuresstruct | MQTTLenString | | struct | MQTTProperty | | struct | MQTTProperties | | struct | MQTTLenString | struct | MQTTProperty | | struct | MQTTProperties | ||||||
+Macros | | | |||||||||
+Typedefs | | ||||||
+Enumerations | |||||
| enum | MQTTPropertyTypes { MQTTPROPERTY_TYPE_BYTE , MQTTPROPERTY_TYPE_TWO_BYTE_INTEGER @@ -171,40 +151,25 @@ Enumerations | ||||
Go to the source code of this file.
+Enumerations | |||||
+Functions | | ||||||
+Data Structuresstruct | MQTTSubscribe_options | | | struct | MQTTSubscribe_options | ||||
+Macros | | ||||||
+Typedefs | | ||||||
This client library supports two modes of operation. These are referred to as synchronous and asynchronous modes. If your application calls MQTTClient_setCallbacks(), this puts the client into asynchronous mode, otherwise it operates in synchronous mode.
@@ -95,7 +82,7 @@ $(function(){ initResizable(false); });You must not call a function from this API from within a callback otherwise a deadlock might result. The only exception to this is the ability to call connect within the connection lost callback, to allow a reconnect.
When using MQTT 5.0, you can also call connect from within the disconnected callback, which is invoked when the MQTT server sends a disconnect packet. This server behaviour is allowed in MQTT 5.0, but not in MQTT 3.1.1, so the disconnected callback will never be invoked if you use MQTT 3.1.1.
-In particular, you must make a publish call within the message arrived callback. These restrictions are all lifted in the MQTTAsync API.
+In particular, you must not make a publish call within the message arrived callback. These restrictions are all lifted in the MQTTAsync API.
If no callbacks are assigned, this will include the message arrived callback. This could be done if the application is a pure publisher, and does not subscribe to any topics. If however messages are received, and no message arrived callback is set, or receive not called, then those messages will accumulate and take up memory, as there is no place for them to be delivered. It is up to the application to protect against this situation.
| MQTTClient.h | |
| MQTTClientPersistence.h | This structure represents a persistent data store, used to store outbound and inbound messages, in order to achieve reliable messaging |
| MQTTProperties.h | |
| MQTTReasonCodes.h | |
| MQTTSubscribeOpts.h | |
| MQTTClient.h | |
| MQTTClientPersistence.h | This structure represents a persistent data store, used to store outbound and inbound messages, in order to achieve reliable messaging |
| MQTTProperties.h | |
| MQTTReasonCodes.h | |
| MQTTSubscribeOpts.h |
An MQTT client library in C.
© Copyright 2009, 2025 IBM Corp., Ian Craggs and others
-Version 1.3.14
+Version 1.3.15
These pages describe the original more synchronous API which might be considered easier to use. Some of the calls will block. For the new totally asynchronous API where no calls block, which is especially suitable for use in windowed environments, see the MQTT C Client Asynchronous API Documentation. The MQTTClient API is not thread safe, whereas the MQTTAsync API is.
An MQTT client application connects to MQTT-capable servers. A typical client is responsible for collecting information from a telemetry device and publishing the information to the server. It can also subscribe to topics, receive messages, and use this information to control the telemetry device.
MQTT clients implement the published MQTT v3 protocol. You can write your own API to the MQTT protocol using the programming language and platform of your choice. This can be time-consuming and error-prone.
@@ -145,7 +132,7 @@ Free any memory being used by the clientThe MQTT protocol provides three qualities of service for delivering messages between clients and servers: "at most once", "at least once" and "exactly once".
@@ -100,7 +87,7 @@ $(function(){ initResizable(false); });#include <MQTTClient.h>
+Data Fields | | | | | | | | | | | | | | | | | | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MQTTClient_sslProperties defines the settings to establish an SSL/TLS connection using the OpenSSL library. It covers the following scenarios:
#include <MQTTClient.h>
+Data Fields | | | | | | | | | | | | | } | binarypwd | | | | | | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MQTTClient_connectOptions defines several settings that control the way the client connects to an MQTT server.
Note: Default values are not defined for members of MQTTClient_connectOptions so it is good practice to specify all settings. If the MQTTClient_connectOptions structure is defined as an automatic variable, all members are set to random values and thus must be set by the client application. If the MQTTClient_connectOptions structure is defined as a static variable, initialization (in compliant compilers) sets all values to 0 (NULL for pointers). A keepAliveInterval setting of 0 prevents correct operation of the client and so you must at least set a value for keepAliveInterval.
Suitable default values are set in the following initializers:
#include <MQTTClient.h>
+Data Fields | | | | ||||||||||||
Options for the MQTTClient_createWithOptions call
-Whether the MQTT version is 3.1, 3.1.1, or 5. To use V5, this must be set. MQTT V5 has to be chosen here, because during the create call the message persistence is initialized, and we want to know whether the format of any persisted messages is appropriate for the MQTT version we are going to connect with. Selecting 3.1 or 3.1.1 and attempting to read 5.0 persisted messages will result in an error on create.
-
Whether the MQTT version is 3.1, 3.1.1, or 5. To use V5, this must be set. MQTT V5 has to be chosen here, because during the create call the message persistence is initialized, and we want to know whether the format of any persisted messages is appropriate for the MQTT version we are going to connect with. Selecting 3.1 or 3.1.1 and attempting to read 5.0 persisted messages will result in an error on create.
#include <MQTTClient.h>
+Data Fields | | | | ||||||||||||
Initialization options
-#include <MQTTClient.h>
+Data Fields | | | | | | | | | | ||||||||||||||||||||||||||||||
A structure representing the payload and attributes of an MQTT message. The message topic is not part of this structure (see MQTTClient_publishMessage(), MQTTClient_publish(), MQTTClient_receive(), MQTTClient_freeMessage() and MQTTClient_messageArrived()).
-#include <MQTTClient.h>
+Data Fields | | | |||||||||
MQTTClient_libraryInfo is used to store details relating to the currently used library such as the version in use, the time it was built and relevant openSSL options. There is one static instance of this struct in MQTTClient.c
-#include <MQTTClientPersistence.h>
+Data Fields | | | | | | | | | | ||||||||||||||||||||||||||||||
A structure containing the function pointers to a persistence implementation and the context or state that will be shared across all the persistence functions.
-#include <MQTTClient.h>
+Data Fields | | | | | } | payload | | |||||||||||||||||||||||||||||||||||||||||||||
MQTTClient_willOptions defines the MQTT "Last Will and Testament" (LWT) settings for the client. In the event that a client unexpectedly loses its connection to the server, the server publishes the LWT message to the LWT topic on behalf of the client. This allows other clients (subscribed to the LWT topic) to be made aware that the client has disconnected. To enable the LWT function for a specific client, a valid pointer to an MQTTClient_willOptions structure is passed in the MQTTClient_connectOptions structure used in the MQTTClient_connect() call that connects the client to the server. The pointer to MQTTClient_willOptions can be set to NULL if the LWT function is not required.
-#include <MQTTProperties.h>
+Data Fields | | | |||||||||
The data for a length delimited string
-#include <MQTTProperties.h>
+Data Fields | | | | | |||||||||||||||
MQTT version 5 property list
-#include <MQTTProperties.h>
+Data Fields} | value | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Structure to hold an MQTT version 5 property of any type
-#include <MQTTClient.h>
+Data Fields | | | | | | ||||||||||||||||||
MQTT version 5.0 response information
-#include <MQTTSubscribeOpts.h>
+Data Fields | | | | | | ||||||||||||||||||
The MQTT V5 subscribe options, apart from QoS which existed before V5.
-Runtime tracing is controlled by environment variables.
@@ -150,7 +137,7 @@ $(function(){ initResizable(false); });Every MQTT message includes a topic that classifies it. MQTT servers use topics to determine which subscribers should receive messages published to the server.
@@ -103,7 +90,7 @@ A '+' character represents a single level of the hierarchy and is used between d