Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

Questions - 100% Pusher replacement , channels and SPA client #43

Closed
ClaudioVarandas opened this issue Dec 9, 2018 · 1 comment
Closed

Comments

@ClaudioVarandas
Copy link

Hi,

First of all thanks for another great package and another great contribution for the community !!

Im thinking about replacing our existing pusher implemention by this package, my idea is a standalone project just for this , and i mean just to serve websockets.

I had a quick look on the documentation, i think i didn't miss anything, so and i have some questions:

Sorry if the answers are in the docs, i think not.

  • can i completly replace pusher ?
  • its possible to have private and public channels ?
  • How can we integrate laravel-websockets in a SPA (vuejs) app ? Laravel echo ? I just need the technical info, bc if possible and no right package we can build a js package.

Thanks
CV

@snellingio
Copy link
Contributor

  1. You can completely replace pusher from the standpoint of laravel's Broadcasting (https://laravel.com/docs/5.7/broadcasting). Pusher has other products available.

  2. Yes it's possible to have public, private, and presence channels.

  3. It works out of the box with laravel echo.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants