You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/iot-agent-json.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ A direct comparison of the two IoT Agents can be seen below:
55
55
| HTTP commands posted to a well-known URL - response is in the reply | HTTP commands posted to a well-known URL - response is in the reply | Communications Handshake |
56
56
| MQTT devices are identified by the path of the topic `/XXX/YYY`| MQTT devices are identified by the path of the topic `/XXX/YYY`| Device Identification |
57
57
| MQTT commands posted to the `cmd` topic | MQTT commands posted to the `cmd` topic | Communications Handshake |
58
-
| MQTT command responses posted to the `cmdexe` topic | MQTT commands posted to the `cmdexe` topic | Communications Handshake |
58
+
| MQTT command responses posted to the `cmdexe` topic | MQTT command responses posted to the `cmdexe` topic | Communications Handshake |
59
59
60
60
As can be seen, the message payload differs entirely between the two IoT Agents, but much of the rest of the protocol
0 commit comments