feat(events): create server event emitter #398
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit creates an event emitter that will serve events in real-time to any client listeners from throughout the application. The current infrastructure uses the native `events` module in NodeJS, but future implementation might take advantage of redis for publish/subscribe. Closes #390.
|
Closing this while I work on a redis implementation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit creates an event emitter that will serve events in real-time to any client listeners from throughout the application. The current infrastructure uses the native
eventsmodule in NodeJS, but future implementation might take advantage of redis for publish/subscribe.Events are cached in a database table
event, with schema defined in #390. When a new client connects, they can download the previous events sending a GET request to the url/events. They can subscribe to real-time events by opening an EventSource to/stream.Closes #390.
Thank you for contributing!
Before submitting this pull request, please verify that you have:
For a more detailed checklist, see the official review checklist that this PR will be evaluated against.
Ensuring that the above checkboxes are completed will help speed the review process and help build a stronger application. Thanks!