-
Notifications
You must be signed in to change notification settings - Fork 10
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
Non-blocking requests #91
Comments
It's possible to deadlock. Amiright |
What kind of deadlock do you see here? I'm always planning to handle responses unboundedly (so Compared to blocking requests ( |
If one actor requests another actor (send message1, wait for response1), and the other actor requests back in the method, (send message2, wait for response2, send response1). It forms a wait-for cycle, message2 is never processed because the first actor is still in the process of requesting. I'm not sure how you implement it, but it's easy to happen. |
Yep, it's a case for blocking requests ( |
API for non-blocking requests.
Something like this:
For the receiving part, nothing is changed.
The text was updated successfully, but these errors were encountered: