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

Allow forcibly disconnecting WebSocket clients #123

Open
4 tasks
rdw-software opened this issue Apr 17, 2023 · 0 comments
Open
4 tasks

Allow forcibly disconnecting WebSocket clients #123

rdw-software opened this issue Apr 17, 2023 · 0 comments
Labels
Complexity: Low Priority: Normal Scope: Runtime Status: Accepted Type: Improvement
Milestone
WebSockets and HTTP

Comments

@rdw-software
Copy link
Member

rdw-software commented Apr 17, 2023 •
edited
Loading

Since the WS protocol is handled by uws, I wasn't sure if this is particularly useful. Maybe for higher-level protocols?

Goals:

  • Can disconnect clients by ID
  • Does nothing if client socket is nullptr
  • Does nothing if no client exists with this ID
  • Returns some sort of error code if it can't disconnect the client

Adding this should be trivial:

  • Find client by UUID
  • If they're not already faded (marked as disconnected):
    • End connection with code/message
  • Error handling (return bool?)

Split off from #73
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: Low Priority: Normal Scope: Runtime Status: Accepted Type: Improvement
Projects
Evo.lua: Timeline
Status: Soon™
Milestone
WebSockets and HTTP
Development

No branches or pull requests
1 participant
@rdw-software