-
Notifications
You must be signed in to change notification settings - Fork 526
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
modify Service Invocation sample #902
Conversation
0be9710
to
99be3ca
Compare
@MregXN A - Appreciate you doing this PR. However for invoke method we only recommend using the http proxy (bring your own client) because this interoperates better with existing code. The SDK is not helpful in this scenario. The |
Sorry for my misunstanding. In reference to your discription in issue #888, which specific SDK functions you wish to utilize? |
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.
Please see my inline comments that hopefully explain what @msfussell and I were thinking.
99be3ca
to
c7f5100
Compare
Signed-off-by: MregXN <[email protected]>
8738975
to
3d9799f
Compare
Signed-off-by: MregXN <[email protected]>
Signed-off-by: MregXN <[email protected]>
@msfussell @paulyuk ready ro review |
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.
LGTM. thank you for the contribution and iterations
Description
Currently the Service Invocation sample in quickstarts are using http request directly. Now they are changed to use dapr client.
Issue reference
Please reference the issue #888 .