-
Notifications
You must be signed in to change notification settings - Fork 49
Add support to gRPC #1088
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
base: main
Are you sure you want to change the base?
Add support to gRPC #1088
Conversation
| case SERVER_STREAMING -> | ||
| handleServerStreaming(workflowContext, methodDescriptor, arguments, call); | ||
| case UNARY, UNKNOWN -> | ||
| handleBlockingUnary(workflowContext, methodDescriptor, arguments, call); |
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.
This should be async (you will need to complete the completable future once the result is provided)
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.
Do you mean to be explicit and controlled, not hidden inside gRPC?
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.
Instead of invoking the whole executor into a completable async and do a blocking call, I guess you can use asyncUnaryCall and make the grpc callback interact with the completable future (one instance that you create) that is returned.
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.
Also I think this whole lambda should be move to grpc executor (and you pass to the executor all the info required by the lamba). I know that we are mixing them in other executors (because intially I was not establishing a clear separation between the builder and the executor) but it is a good practise for clarity purposes.
Signed-off-by: Matheus Cruz <matheuscruz.dev@gmail.com>
Signed-off-by: Matheus Cruz <matheuscruz.dev@gmail.com>
Changes
Do not review yet 😃
TODO
PATHbuilderCloses #1078