Skip to content
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

[ADDED] Name in consumer configuration #580

Merged
merged 2 commits into from Sep 14, 2022
Merged

[ADDED] Name in consumer configuration #580

merged 2 commits into from Sep 14, 2022

Conversation

kozlovic
Copy link
Member

When this is used, the library will send request to a different API subject space where the stream and consumer names are in the subject, along with a filter subject if one is specified.

Signed-off-by: Ivan Kozlovic ivan@synadia.com

When this is used, the library will send request to a different
API subject space where the stream and consumer names are in the
subject, along with a filter subject if one is specified.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Copy link
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kozlovic
Copy link
Member Author

Related to nats-io/nats-architecture-and-design#148

@derekcollison I went with the approach that as long as the new consumer config param "Name" is specified, then the library uses the new subject space, that is, I don't check on server version. The worst case is that the request will timeout. Do you think that checking the server version is required? (of course, always the question: what if client connects to server that is pre 2.9.0 while the server that would handle the request is 2.9.0+ and would be able, but I know that we should have NATS network at the same version level, so I could make the check if you think this is required)

@derekcollison
Copy link
Member

I don't think version check required imo..

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Copy link
Member

@aricart aricart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - the thing I notice, is for new API clients need to validate the durable name to be something acceptable for embedding, because otherwise it will collide with the filter part of the subject.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants