-
Notifications
You must be signed in to change notification settings - Fork 45
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
Blocking API version #26
Comments
Thank you for sharing your concerns 👍 I am not sure how to do this cleanly given our reliance on Tonic. Which part of the async. API do you find the most complex to work with? |
After a short investigation, it seems we would have to duplicate the API using a blocking client |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Clients don't have to be async, it's more the necessity for the server-side components. But this library forces a client to run inside an async runtime introducing unnecessary complexity for many cases.
The text was updated successfully, but these errors were encountered: