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

Possible change to direct methods #28

Open
bocajim opened this issue Nov 4, 2020 · 0 comments
Open

Possible change to direct methods #28

bocajim opened this issue Nov 4, 2020 · 0 comments

Comments

@bocajim
Copy link
Contributor

bocajim commented Nov 4, 2020

Does anyone have any inputs/objections to an alternate direct method implementation that can change the reply to be asynchronous from the callback? I have a use case where I need processing time to handle the callback and I don't want to hold the context, I want to send the reply at a later date.

Possible changes:

  1. Callback provides messageID and then a new function is added that sends a reply when that is invoked
  2. Callback provides a struct with a Reply() method for easy responses (but harder serialization to manage).

I prefer #1 because it is easy to pass the ID between async processing.

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

1 participant