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.

Sign up for GitHub

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

Jump to bottom

Split to TFCALL and TFCALLASYNC #173

Closed
shacharPash opened this issue Aug 16, 2023 · 0 comments · Fixed by #178
Closed

Split to TFCALL and TFCALLASYNC #173

shacharPash opened this issue Aug 16, 2023 · 0 comments · Fixed by #178
Labels
breakingchange API or breaking change

Comments

@shacharPash
Copy link
Contributor

Currently there is the TFCall command with an _async variable that determines whether the TFCALL or TFCALLASYNC command is sent.
We need to decide whether to leave the situation as it is, or add two separate commands: TFCall and TFCallAsync that will call the current TFCall (which will become private) and set the appropriate value in _async.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breakingchange API or breaking change
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Split TFCALL to TFCALL and TFCALLASYNC redis/NRedisStack
1 participant
@shacharPash