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
The file attachment feature allows uEs to "attach" file(s) metadata to any message sent (i.e. for publish, notification, request, response type messages). This feature was missed when we switched from cloudevents to UAttributes so it needs to be added back into the specifications and elaborated on throughout the specs.
When the message is consumed locally, the consumer references the local file address, when the message is sent across the device boundary, the file(s) are uploaded/downloaded based on the file transfer protocol and the file path is then updated in the message to reference the new file location. File transfer is typically done outside of the uTransport communication protocol using an optimized (and often proprietary) file transfer protocol. For the sake of the specifications we will use ftp for example but make it pluggable in the streamer.
This feature will impact the core-api, the language libraries, streamer libraries. this issue will be used to track the development and specification work.
The text was updated successfully, but these errors were encountered:
The file attachment feature allows uEs to "attach" file(s) metadata to any message sent (i.e. for publish, notification, request, response type messages). This feature was missed when we switched from cloudevents to UAttributes so it needs to be added back into the specifications and elaborated on throughout the specs.
When the message is consumed locally, the consumer references the local file address, when the message is sent across the device boundary, the file(s) are uploaded/downloaded based on the file transfer protocol and the file path is then updated in the message to reference the new file location. File transfer is typically done outside of the uTransport communication protocol using an optimized (and often proprietary) file transfer protocol. For the sake of the specifications we will use ftp for example but make it pluggable in the streamer.
This feature will impact the core-api, the language libraries, streamer libraries. this issue will be used to track the development and specification work.
The text was updated successfully, but these errors were encountered: