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.

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 blocking Recipient::send() - or another form of backpressure? #24

Open
strohel opened this issue Feb 20, 2021 · 0 comments
Open
Labels
API Relates to public API surface enhancement New feature or request

Comments

@strohel
Copy link
Member

strohel commented Feb 20, 2021

If I understand the overall architecture right, the "flow control" using actor feels most natural when there are slow producers and fast consumers. Or if dropping messages is fine.

In the other case, the channels would quickly become full. Senders receive a specific error in that case, but it is not clear how they should react. Simply sleeping is prone to reduce throughput, and may require tuning.

A blocking variant of send() could help here, but it could open a Pandora's box at the same time (e.g. how to shut down a blocked actor?). I.e. this may be a complex topic.

This is probably not a Before Release material. The ticket serves mainly to get people's feedback.

@strohel strohel added API Relates to public API surface enhancement New feature or request labels Feb 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Relates to public API surface enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant