Conversation
Can be necessary to queue messages, if sever is slow to connect.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We have found this problem with a video server we connect via Rtsp.
Nx Meta server is slow connecting, so, we need to queue the messages, since they would be lost, if keep the old way.
So, I am queueing the messages, instead of direct sending (since from connect, that we set in an async task, and playing/pause messages, the connect can be still in setup).
I have not a test ready, since I have tried with different cameras/video server, and works correctly (sorry, I am not good with automated testing, and honestly, I don't know how to implement for this change)