Repository navigation
NATS: proposal to change/augment spec to use message headers #1006
Description
Activity
@derekcollison thoughts?
I think both options should be available. Be great to have header support for those who prefer binary payloads.
Reacted by Byron Ruth@bruth yup! Just ping @derekcollison when you submit the PR so he can review it as he's our expert in that space
As of NATS 2.2 message headers have been supported (NATS is currently 2.8.2 for reference).
This issue is to propose change the protocol binding to put all fields into the header and have the
datamap to the message payload exclusively. This would remove the need of the JSON-encoded representation for all of the event attributes.If this is a welcome change, I am happy to open a PR to change the document. Note these are not mutually exclusive, so for NATS servers that pre-date v2.2.x, the JSON encoded representation could still be maintained.