Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ability to get socket identifier #5

Open
andreaselia opened this issue Nov 17, 2021 · 2 comments
Open

Ability to get socket identifier #5

andreaselia opened this issue Nov 17, 2021 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@andreaselia
Copy link

It would be pretty nice to be able to use the socket connection identifier for cases where you may want to ping a message to other clients from say a backend API, without pinging the sender.
@andrewsmedina
Copy link
Contributor

andrewsmedina commented Nov 17, 2021 •
edited
Loading

@andreaselia I don't know if I have understood. Are you talking about authenticated channels?

@andreaselia
Copy link
Author

andreaselia commented Nov 17, 2021 •
edited
Loading

@andrewsmedina an example better to what I mean would be in Laravel you're able to broadcast "toOthers" which relies on having the current socket identifier so the the event doesn't get fired to the sender.

Andreas triggers an event that gets send to the backend
backend sends the event toOthers
Andrews receives the event triggered by the backend, but Andreas does not

@andrewsmedina andrewsmedina added the help wanted Extra attention is needed label Nov 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@andrewsmedina @andreaselia