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

Don't start a new chain of requests when previous is not done #12

Open
birgitta410 opened this issue Jul 18, 2016 · 0 comments
Open

Don't start a new chain of requests when previous is not done #12

birgitta410 opened this issue Jul 18, 2016 · 0 comments

Comments

@birgitta410
Copy link
Owner

In cases where readData takes a long time (lots of pipelines, slow network, ...), depending on the callers time interval, the next readData call will go ahead even when the previous responses have not all come back yet. That leads to performance problems.

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