Skip to content

Support Redis/Websocket #3

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.

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

Open
zerario opened this issue Oct 21, 2024 · 0 comments
Open

Support Redis/Websocket #3

zerario opened this issue Oct 21, 2024 · 0 comments

Comments

@zerario
Copy link
Owner

zerario commented Oct 21, 2024

Recent announcement:

So, there's going to be a bunch more things coming soon but I wanted to share for those of you who likes to create things for PiShock a new way to interact with it.

Introducing DOCUMENTATION for direct Redis or Websocket connection to operate the shockers. This will keep the latency very low.

The documentation will be reformatted shortly, but I wanted to share with everyone that it exists.

https://pishock.notion.site/Redis-Connection-Documentation-Ops-ShareCodes-65e3b131cfe942e885a61a0d933377bf

https://docs.pishock.com/pishock/redis-direct-connection.html
https://docs.pishock.com/pishock/obtaining-user-id-and-token.html
https://docs.pishock.com/pishock/websocket-api.html

Websocket brokers connections to redis, but
If we change stuff at some point the broker's likely to stay
and the login to redis assumes you've called IsTokenValid() yourself or verified API keys ahead of time or just fail the connection
The call to IsTokenValid would need to be... with registerACLs=true

@zerario zerario mentioned this issue Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant