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

EventManager getResponses doesn't take timestamp #13

Closed
jtmelton opened this issue Oct 5, 2014 · 1 comment
Closed

EventManager getResponses doesn't take timestamp #13

jtmelton opened this issue Oct 5, 2014 · 1 comment
Assignees
Labels

Comments

@jtmelton
Copy link
Owner

jtmelton commented Oct 5, 2014

Reported by a user - copying bug report from email:

"The EventManager doesn't take a timestamp - how do I say which responses I need based on time, like if a server fails and I need to get responses from when it was down?"

@jtmelton jtmelton added the bug label Oct 5, 2014
@jtmelton jtmelton self-assigned this Oct 5, 2014
jtmelton added a commit that referenced this issue Oct 5, 2014
EventManager made an assumption you wanted events from the most recent 2
hours, which is obviously invalid. The client should be able to specify
the starting time for which they want responses. The event manager
should then return responses from that time forward.
@jtmelton
Copy link
Owner Author

jtmelton commented Oct 5, 2014

EventManager made an assumption you wanted events from the most recent 2 hours, which is obviously invalid. The client should be able to specify the starting time for which they want responses. The event manager should then return responses from that time forward. This issue has been resolved.

@jtmelton jtmelton closed this as completed Oct 5, 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