|Re: Where the MQTT messages has been decoded using the google protobuf? [message #1768712 is a reply to message #1768676]
||Fri, 21 July 2017 22:29
| David Woodard
Registered: July 2014
If you are using the CloudService of Kura to send/receive messages, you do not need to worry about Google Protobuf. The framework handles the encoding/decoding for you. The classes that handles this can be reviewed here .
I am not sure I understand your statement about a normal MQTT client. If you send a message with the Kura CloudService, and you receive that message with a non-Kura MQTT client (i.e. stand alone Paho client), you will need to decode the message yourself. If you are not decoding the message with the "normal MQTT client", then you are not using the Kura CloudService. There are other levels of transport within Kura, namely the DataService. If you are using the DataService, then messages are not encoded with Google Protobuf, and you don't need to worry about decoding .
One other note, the latest version of Kura (v3.0.0) introduced simple JSON formats to the CloudService. If you are using this, then you also don't need to worry about decoding the message. This is not the default setting of Kura, but can be enabled if desired.
Powered by FUDForum
. Page generated in 0.01527 seconds