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

More protocol friendly request pattern. #158

Closed
ColinSullivan1 opened this issue May 30, 2017 · 5 comments
Closed

More protocol friendly request pattern. #158

ColinSullivan1 opened this issue May 30, 2017 · 5 comments

Comments

@ColinSullivan1
Copy link
Member

Add functionality to mirror the go-nats feature, https://github.com/nats-io/go-nats/pull/295.

@sixlettervariables
Copy link
Collaborator

sixlettervariables commented May 30, 2017

If I'm reading this correctly, does the following describe that behavior?

  • Each client (when initiating the first request) would create a connection local inbox
  • The client (read: per connection) would subscribe to that inbox as a wildcard
  • Each request from the client would have a reply to referencing that inbox plus a unique ID
  • The reply would be dispatched locally based on that unique ID

@ColinSullivan1
Copy link
Member Author

@sixlettervariables , were you thinking of contributing here?

@sixlettervariables
Copy link
Collaborator

As I understand it we, basically, do exactly this in our usage of the client (but for a different purpose than performance). Trying to understand the feature and how it may/may not affect us.

@ColinSullivan1
Copy link
Member Author

It really shouldn't affect you (beyond better performance), unless you have some subject based authorization enabled that would interfere with the internal subscription.

@ColinSullivan1
Copy link
Member Author

Resolved by #167.

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

No branches or pull requests

2 participants