-
Notifications
You must be signed in to change notification settings - Fork 119
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
Support reactive/non-blocking requests #269
Labels
Comments
Thanks to the recent work on decoupling the implementation of API endpoints from the underlying HTTP client, this should be more feasible to achieve. It's on the roadmap, but no concrete timeline yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the Nexmo Library is backed by a HttpClient using a PoolingHttpClientConnectionManager which is a blocking client.
Whilst it would represent a lot of work it would be good to get non-blocking implementation (eg usin RxJava or Reactor) of the interfaces to allow for use in non-blocking codebases.
The text was updated successfully, but these errors were encountered: