MQTTASYNC_RESPONSEOPTIONS(3)
π MQTTAsync_responseOptions π
okay so bestie, welcome to the MQTTAsync_responseOptions page from the Library Functions Manual β it's giving struct-that-defines-your-call-options energy and honestly? iconic. sit down, grab a strawberry π, we're doing this together.
β¨ SYNOPSIS β¨
#include <MQTTAsync.h>
π Data Fields π
char struct_id [4]int struct_versionMQTTAsync_onSuccess * onSuccessMQTTAsync_onFailure * onFailurevoid * contextMQTTAsync_token tokenMQTTAsync_onSuccess5 * onSuccess5MQTTAsync_onFailure5 * onFailure5MQTTProperties propertiesMQTTSubscribe_options subscribeOptionsint subscribeOptionsCountMQTTSubscribe_options * subscribeOptionsList
πΈ Detailed Description πΈ
So this whole struct is literally just the structure that defines your call options, periodt. π
But wait β for MQTT 5.0 there's input data going on and stuff describing the response method, so the glow-up happened and now there's also a synonym: MQTTAsync_callOptions, which lowkey reflects how you actually use it way better. π¦
The responseOptions name? Yeah, it's still here. Kept for backward compatibility β we respect our elders in this house. π«Ά
π¦ Field Documentation π¦
char struct_id[4]
The eyecatcher for this structure. Has to be MQTTR β no negotiating, bestie, it's the vibe check for the struct. π
int struct_version
The version number of this structure. Must be 0 or 1. And if it's 0? Then there are no MQTTV5 options, that's just the deal. π
MQTTAsync_onSuccess* onSuccess
A pointer to a callback function that gets called if the API call successfully completes. You can set it to NULL β but then you get no indication of successful completion at all, so like... your call. π
MQTTAsync_onFailure* onFailure
A pointer to a callback function that gets called if the API call fails. Can also be NULL, in which case you get no indication of unsuccessful completion β and honestly, the silence is deafening. π
void* context
A pointer to any application-specific context you want. This context pointer gets passed to your success or failure callback functions, so your callbacks can actually reach the context info. It's the little string tying it all together. π
MQTTAsync_token token
A token gets returned from the call, and you can use it to track the state of this request β both inside the callbacks and in future calls like MQTTAsync_waitForCompletion. This one is output only β any change made by the application will be ignored. Don't touch, bestie, it's not yours. π«
MQTTAsync_onSuccess5* onSuccess5
A pointer to a callback function to be called if the API call successfully completes. Can be set to NULL, in which case no indication of successful completion will be received. Same deal, the sequel. β¨
MQTTAsync_onFailure5* onFailure5
A pointer to a callback function to be called if the API call successfully completes. Can be set to NULL, in which case no indication of successful completion will be received. (Yes, that's exactly what it says β we report, we don't editorialize. π
)
MQTTProperties properties
MQTT V5 input properties. That's it, that's the whole field. π
MQTTSubscribe_options subscribeOptions
No description given, it just exists and slays in silence. π
int subscribeOptionsCount
Also no description. Just a count, living its truth. β
MQTTSubscribe_options* subscribeOptionsList
Also no description β a pointer to a list, being mysterious, main character energy. π§
π Author π
Generated automatically by Doxygen for Paho Asynchronous MQTT C Client Library from the source code. Not a human, not a bestie, just a robot doing its thing. π€
ngl this page came straight out of the Paho Asynchronous MQTT C source, dated Tue Jun 2 2026 00:00:00, and it's filed under MQTTAsync_...onseOptions(3) in case you ever need to find it again. mwah, bye bestie! π«Άπ
π¦ where this page comes from
- fedora 44: paho-c-devel 1.3.16-1.fc44 Β· BSD-3-Clause AND EPL-2.0
- fedora 44: paho-c-devel 1.3.16-1.fc44 Β· BSD-3-Clause AND EPL-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms