This repository has been archived by the owner on Feb 7, 2024. It is now read-only.
[2.x] Dispatch events on actions #556
Merged
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
…avel-websockets into feature/dispatched-events
|
Can you please explain how to use this? |
|
yes, it is completely mystery how to use this.. there is no any documentation available. it is weird that laravel/websockets does not provide server level WebSocket connection control like new connection or disconnection and etc.. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Added events dispatch on various actions throughout the server (like new connections, channel subscriptions, etc.) that can be easily handled by the Laravel events observers outside the server, now that the async queue driver exists and can be used for listeners to avoid any blocking I/O.