-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for NGS #63
Comments
It looks like there's a solution to this but this branch hasn't been merged to master. I was about to start doing some experimentation with resgate and noticed that it didn't seem to support NATS 2.0 authentication (a requirement for my production scenario). Is this blocked on something @jirenius ? |
Perhaps it was blocked on the official release of NATS 2.0- NGS uses the same mechanism. The branch looks ready... BTW, not required, but an example unit test can be found here. |
This branch wasn't merge because it didn't fully support NGS. One feature was still missing: the ability to know if a message might have been lost within a super-cluster (eg. through something like a super-cluster node disconnect event). But since support for authentication credentials is a stand-alone feature, I will have it merged to develop right away. @autodidaddict , I can mail you new binaries (which architecture?) with authentication support if needed, or post them for you on https://forum.resgate.io . Thanks @ColinSullivan1 ! That helps when creating the unit tests for it. |
Issue
Add support to connect Resgate to NGS.
The text was updated successfully, but these errors were encountered: