feat(client): websocket #1904
Closed
feat(client): websocket #1904
Conversation
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
|
We decided to limit the client to the UI version info -- it will still receive messages when sessions change, but we don't need to query APIs to refresh the local status. Move that to a new issue |
|
superseded by #2013 |
This was referenced Apr 4, 2023
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 is a preliminary stub for the client-side WebSocket code. Mind that most of the logic is missing.
To simulate the client connection, you can use Postman.
The address for the connection is
wss://<deployment>.dev.renku.ch/ui-server/ws.Remember to provide the cookies in the headers for
ui-server-sessionRefer to #1338 and #1903 for further explanations. It contains the server-side code from #1888
/deploy #persist