Quite cool

[gedw99]

Just wanted to say how cool this project is.

I have yet to play with it but have a few newbie questions:

there is only http. No plans to add websockets / SSE for pushing out to web clients ?

Am stil a bit confused about what is listening to a subscription. I presume it is caddy and so you end up with chains / pipelines of pub / sub / pub , etc ?

are you going to use nats to update the caddy config itself across many caddy servers worldwide ? Sort of like a management channel

[codegangsta]

Hey @gedw99, thanks for looking into this.

This implementation is just a start, so there is still plenty more to do feature-wise, and contributions are of course welcome.

there is only http. No plans to add websockets / SSE for pushing out to web clients ?

I'll probably want to document this, but you can support websockets with the Caddy Layer 4 plugin. I've worked with multiple organizations that will put NATS behind a proxy to do more advanced TLS or better support mTLS with thinks like hardware security modules and the like, same concept works with Caddy.

Am stil a bit confused about what is listening to a subscription. I presume it is caddy and so you end up with chains / pipelines of pub / sub / pub , etc ?

This module will create the subscriptions for you, bound to the NATS context you have specified, just like the NATS CLI does. Most of the work this module does is to help you semantically map HTTP requests to NATS requests and visa-versa, there are probably a ton more cool features to implement as well though.

are you going to use nats to update the caddy config itself across many caddy servers worldwide ? Sort of like a management channel

So I'd love to do something like this in the future, it's a great idea and maybe something you can add an issue for? I'd imagine Caddy could watch a KV store in JetStream for updating it's config and reloading.