-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
bi-directional WebSocket support and/or message queue/pools #199
Labels
Comments
17 tasks
3 tasks
Agree that this would be good to have, and with the introduction of request events on For now, I'm going to close this issue and fold it into #2492 since that one has a bit more support, but covers the same ground as this. |
This was referenced Jul 28, 2021
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
Would be great to have the ability to watch a bi-directional web socket to process messages from the back-end as they are received.
Use Case:
User preforms a action through the front-end which actions several back-end events. It would be great if we could monitor that these different events did occur (there is an endless amount of different events and combinations of events).
What would be great if there was a simple message pool/queue or a way to "monitor" a bi-direcitonal websocket and capturing the messages received from the back-end.
We would then write tests to check if those events are being executed by looking at the socket/pool/queue and seeing if the events were received after X user actions.
The text was updated successfully, but these errors were encountered: