-
Notifications
You must be signed in to change notification settings - Fork 25
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
Make rpc.go so it can use a single link and send/receive multiple messages #52
Make rpc.go so it can use a single link and send/receive multiple messages #52
Conversation
… the channel if they cancel the wait.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed and added a few suggestions to improve the code.
looks good. about to test it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tentative approval as I'm out and don't want to block on this getting in.
Once you and @serbrech are happy with it and confident it works please merge and tag.
- Do a type check when casting for CorrelationID. For now, just ignore those uncastable messages.
…it anymore after that).
Service Bus and Event Hubs both allow you to send multiple messages on the management link. We weren't using this and it meant that we were creating a separate link per request.
This PR changes that so we pass in a unique message ID for each request, which allows us to demux the requests in the client, thus only using a single link.
This is how the other track 2 SDKs currently handle it.