Update WRP Spec for deviceID #53
Conversation
|
Kudos, SonarCloud Quality Gate passed!
|
content/docs/wrp/simple-messages.md
Outdated
| source | The device_id name of the device originating the request or response. | ||
| dest | The device_id name of the target device of the request or response. | ||
| content_type | (optional) The media type of the payload. | ||
| source | The device_id name of the device originating the request or response (i.e. dns:tr1d1um.example.net for inbound messages). |
There was a problem hiding this comment.
I wonder if parodus is or plans to use the source field (dns:tr1d1um.example.net) on inbound messages.
There was a problem hiding this comment.
I thought parodus uses the source at the very least to fill in the destination for the response wrp it sends. I could be wrong.
| source | The device_id name of the device originating the request or response (i.e. dns:tr1d1um.example.net for inbound messages). | ||
| dest | The device_id name of the target device of the request or response (i.e. mac:112233445566/config for inbound messages). | ||
| device_id | The canonical device ID (i.e. mac:112233445566) involved in this envelope. It defers from source or dest in that no further parsing is required to extract the ID from the value. | ||
| content_type | (optional) The media type of the payload. If not specified on inbound messages, `application/octet-stream` is used as default. |
There was a problem hiding this comment.
I thought we were only adding this for events? Is this also being added to request-responses?
There was a problem hiding this comment.
Nevermind, found the pull request (xmidt-org/webpa-common#508). But isn't it filled in for outbound messages, not inbound?
Co-authored-by: Kristina Pathak <[email protected]>
|
Kudos, SonarCloud Quality Gate passed!
|
No description provided.