You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you, @moneya, for your interest.
This PoC (proof of concept) currently implements a simple broadcast, that is, the client sends a message to the server, and the server takes care of delivering this message to all connected clients (broadcast).
The client-client communication should still go through the server specifying the recipient. It is possible to redefine the default WebSocketHandler by extending the WebSocketHandlerInterface interface. To set a new WebSocketHandler you can use the setWebSocketHandler method in the LaraSockCommand.
Honestly, I had slowed down the development of this PoC because of the little feedback I received. But if there is interest, it can be resumed.
Well, does this work with pusher package / protocol?
In pusher there's this .whisper() function we using for (user is typing).
I think that's client to client.
And so client to server works and server to client works right now?.
Do I need a route , like the below to register an handler?
I have been following this project for a while, since you started.
But didn't checkback until now.
And yes am interested in this project.
I need a swoole alternative to laravel websocket package.
Hi, I would to know if this supports bi-directional communication via websocket.
I currently use laravel websocket but would like to switch to swoole.
If yes, can you point me to a documentation for that?
do you support custom route base channels?
i currently use laravel websocket to handle that.
https://beyondco.de/docs/laravel-websockets/advanced-usage/custom-websocket-handlers
The text was updated successfully, but these errors were encountered: