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.

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

Simulate Keepalive Message Interruption [Feature Request] #291

Closed
1 task done
Robertsmania opened this issue Nov 5, 2023 · 1 comment · Fixed by #303
Closed
1 task done

Simulate Keepalive Message Interruption [Feature Request] #291

Robertsmania opened this issue Nov 5, 2023 · 1 comment · Fixed by #303
Assignees
Labels
enhancement New feature or request

Comments

@Robertsmania
Copy link

Tell us about your feature request

For testing client logic to handle KeepAlive Messages it would be helpful to have an option with the CLI to suspend or interrupt the outgoing messages.

I'm not certain of the causes or conditions that could cause a real server in production to stop sending the messages, but from the documentation it sounds like the connection itself is still considered open (or at least has not received an explicit close).

Ideally, the option with the CLI would stop sending the Keepalive Messages to an existing client but not prohibit establishing new connections which would receive the messages as normal. Perhaps specifying the SessionID to suspend?

Disclaimer

  • I agree
@Robertsmania Robertsmania added the enhancement New feature or request label Nov 5, 2023
@Xemdo
Copy link
Contributor

Xemdo commented Dec 27, 2023

This will be implemented as such:

twitch event websocket keepalive --session=[Session ID] --enabled=[true/false]

@Xemdo Xemdo self-assigned this Dec 27, 2023
Xemdo added a commit that referenced this issue Dec 30, 2023
Added RPC command to disable keepalive messages for a client; #291
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants