edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QUARKS-175) IoT Platform command processing not correctly handling json.
Date Tue, 10 May 2016 00:02:12 GMT

     [ https://issues.apache.org/jira/browse/QUARKS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel John Debrunner updated QUARKS-175:
-----------------------------------------
    Summary: IoT Platform command processing not correctly handling json.  (was: IoT Platform
commands processing not correctly handling json.)

> IoT Platform command processing not correctly handling json.
> ------------------------------------------------------------
>
>                 Key: QUARKS-175
>                 URL: https://issues.apache.org/jira/browse/QUARKS-175
>             Project: Quarks
>          Issue Type: Bug
>          Components: Connectors
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>
> IotDevice.commands() returns the commands information as a JSON object.
> With Iot Platform (IotfDevice) the key "payload" contains the complete MQTT message rather
than extracting the command data (the "d" key in the MQTT message).
> An IoT Platform message contains two keys, "d" and "ts".
> * "d" is the data for the message
> * "ts" is an optional ISO8601 timestamp
> The intention was that the "payload" key be the payload of the command (not the message)
for the json format to simplify code for others, and also not force every application to have
to fetch the "d" key.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message