Add event stream starting with video processing event #9
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
sneakycrow
force-pushed
the
event-stream
branch
from
6344dbb
to
764a8ea
Compare
sneakycrow
force-pushed
the
event-stream
branch
from
764a8ea
to
fe0290e
Compare
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.
A video processing event is a trigger on the
processing_statuscolumn forvideos. This update adds a listener for that trigger as well as a websocket connection for the client.When a new notification comes through while an open ws connection exists, it sends those notifications to the client.
Notable, this is not secured yet and it sends all notifications to the client. We'll need to update with auth/filtering.