-
Notifications
You must be signed in to change notification settings - Fork 106
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
Library doesn't allow async processes #24
Comments
Hi @faizann can you kindly explain your concern? We are currently working on a very large python project and we are concerned with your findings. Is there a way we can reproduce this issue? We have done several stress tests with no impact that we have noticed. |
It has been a while since I looked at this code. We decided not to use Python library and went with GO as a language for better async processing. All in all it is just python and the architecture of python that limits the most. |
Hi
I have noticed that once run is called the library goes into a loop of reading/blocking on websocket. This means that you lose control on your process after calling run.
This makes building multiprocessing/multithreaded applications impossible.
I suggest a way to make the reading part non-blocking so that app can do other things like use queues for multiprocessing. I suspect this library will not work very well on high loads where ARI apps has to do DB queries or making other HTTP API calls that can take a few seconds to respond.
The text was updated successfully, but these errors were encountered: