[
https://issues.apache.org/jira/browse/QUARKS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335975#comment-15335975
]
Dale LaBossiere commented on QUARKS-176:
----------------------------------------
[[email protected]], MqttDevice's command() and event() methods
javadoc, and/or the class level javadoc, need to clarify the payload formats
both in the JsonObject tuple and in the actual MQTT message payload. The
overall JsonObject tuple content is covered by IotDevice interface.
At a high level MqttDevice prescribes only minimal constraints on the MQTT
message's payload. Details of the content format is the application's domain.
As Dan noted, the code provides the clues.
The DeviceCommsApp and SensorAnalyticsApplication samples use MqttDevice if you
want to explore that.
I'll mark this in-progress. Thanks!
> MQTT IotDevice implementation does not document message format.
> ---------------------------------------------------------------
>
> Key: QUARKS-176
> URL: https://issues.apache.org/jira/browse/QUARKS-176
> Project: Quarks
> Issue Type: Task
> Components: Connectors
> Reporter: Daniel John Debrunner
>
> The actual format of the MQTT message payload for device events and commands
> is not documented.
> Non-Quarks clients need to know the format to process events or send commands.
> Looking at the code it looks like it's simply the UTF-8 representation of the
> JSON for the event or commands. That is the MQTT IoTdevice doesn't add in any
> additional information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
