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

The TickSpout is only emitting ticks in nextTuple() which means it's very likely the ticks could get out of sync. #37

Open
cjnolet opened this issue Sep 12, 2014 · 0 comments
Labels
Milestone

Comments

@cjnolet
Copy link
Member

cjnolet commented Sep 12, 2014

A better option would be to have a TimerTask running that is emitting tuples directly instead of using nextTuple(). This would guarantee tick tuples are always prioritized. It's possible it could cause issues in cases where there is significant back-pressure... but we'll need to verify this through some stress tests.

@cjnolet cjnolet added the bug label Sep 12, 2014
@cjnolet cjnolet added this to the 0.3.0 milestone Oct 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant