-
Notifications
You must be signed in to change notification settings - Fork 422
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
Add support for a service response callback with request payload embedded #35
Comments
@tfoote can you add more info for this issue? I'm feeling a bit out out of context here. Thanks! |
This was mostly in the context of an async service. Where at the time of response the initial request may be out of scope. In that case the response could be coupled with the request. For example here you could print both the request and the result instead of just the result. This saves the user from having to book keep which request is associated with which response if they're running multiple in parallel, which is not represented in the simple example. |
…ecutor Documentation updates
Remove check argument for null from int64_t
This was identified as potentially valuable during the parameter API review.
The use case is that there are a sequence of queries in a request, the response objects can be sorted in the same order as the requests, instead of requiring the response to be entirely self describing.
The text was updated successfully, but these errors were encountered: