Socket.io enhancements

[1618033]

• Fixed channel namings; private & presence
• Did necessary changes to support socket.io v1.4.8
• Enable client to send messages to server (request)

[tlaverdure]

Since the Laravel Echo Server does not currently support receiving client events I would hold off on this update. I do think that there is a good use case of this though, and pusher does support this: https://pusher.com/docs/client_api_guide/client_events#trigger-events

Would make sense for high capacity collaboration apps that emit a ton of arbitrary input events (mousemove, click, keypress, etc). As this may be up for discussion, I don't want it to slow things down so I've submitted another PR to fix the private and presence prefixes. Laravel Echo Server 1.0 will be out soon.

[1618033]

Made a pull request to Laravel Echo Server to support requests from client.

Thanks and regards!

On Sat, Sep 10, 2016 at 11:13 AM, Thiery Laverdure <notifications@github.com

wrote:

Since the Laravel Echo Server does not currently support receiving client
events I would hold off on this update. I do think that there is a good use
case of this though, and pusher does support this:
https://pusher.com/docs/client_api_guide/client_events#trigger-events

Would make sense for high capacity collaboration apps that emit a ton of
arbitrary input events (mousemove, click, keypress, etc). As this may be up
for discussion, I don't want it to slow things down so I've submitted
another PR #44 to fix the private
and presence prefixes. Laravel Echo Server 1.0 will be out soon.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#43 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ASC55JrywlgZx-eVSQW3JpSBh4zhgfhbks5qotdBgaJpZM4J5pyS
.

[taylorotwell]

Closing for now.

[vesper8]

Would love to see this added to Laravel Echo and Laravel-Echo-Server!

[zdnk]

Any update or progress on this? @taylorotwell @1618033