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

Try to support back pressure with reactive streams #2

Open
OndroMih opened this issue Mar 17, 2017 · 0 comments
Open

Try to support back pressure with reactive streams #2

OndroMih opened this issue Mar 17, 2017 · 0 comments

Comments

@OndroMih
Copy link
Member

Current solution doesn't support back pressure - if multiple pathfinder instances exist, all of them provide routes in parallel nad can provide more routes than necessary. The monolith client has to accept all the routes, it only has an option ignore them, not to throttle or cancel the computation.

Reactive streams offer a publish-subscribe concept, where subscriber requests a limited amount of data, and can request more if ready for them. Publisher wouldn't send more data than requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant