Support headers

Hi,

First of all thanks for offering to the community this library as well as all the NATS ecosystem.

I saw in the Projects section that header support is included in the v1.0.0 milestone.

We’re quite in need of this feature, and have a working solution where we enforce some schema on message data, something like:

{
  "__data__": <actual_data>,
  "__context__": <trace_context>
}

The problem with this approach, is that we MUST serialize all our messages to JSON format (we could use another format, but the constraint of enforcing schema on the payload is the same).

BTW we also use Typescript, and had to implement this feature too using ts-nats

We’re in the process of rewriting our internal library, and are wondering if we should port this “solution” to our new version, or if we should wait for this feature to be implemented in nats.py.

If you could give us a time estimate of the implementation, it would help us in taking a decision.

More over, I’m not familiar with NATS code base, and don’t really know how to tackle this issue, but if there are things that seem doable for first contributors, don’t hesitate to point us in the right direction.

Thanks in advance 🙇

[gcolburn]

Hi @wallyqs. Any updates on an estimated timeline for header support in nats.py? Thanks!

[reegeek]

Hi @wallyqs thank you for all work already done. I use nats to communicate between a server write in .net and a client in python. I use header in C#, I would like to use it also in python. Do you have any visibility as to when headers will be taken into account in python ? Regards