feat: add MQTT transport messaging #459
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Add MQTT as a
Messageformat.Description
This commit adds
MQTTto the supported transport protocols by adding aBindingand theMQTTMessage<T>type, extending the baseMessagetype, adding the MQTT fields forpayload,PUBLISHandUser Properties. Thepayloadfield directly maps toMessage#body, whileUser Propertiesroughly maps toMessage#headers, even though the properties here are not formatted with ace-prefix like other transport protocols. This is per the spec. See: https://github.com/cloudevents/spec/blob/v1.0.1/mqtt-protocol-binding.md. ThePUBLISHproperty is there primarily to support the"Content type"and perhaps should be typed better. Feedback welcome.