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

commands: Adding "disconnect" command to force socket shutdown #1057

Merged
merged 3 commits into from
Feb 26, 2023

Conversation

inemajo
Copy link
Contributor

@inemajo inemajo commented Feb 21, 2023

Hi, this pull request add a "disconnect" command, usefull when your connection change and you want to force closing the socket for reconnect

Copy link
Owner

@hrkfdn hrkfdn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Generally this looks good to me. While it is technically more correct to call it disconnect, I'm wondering if we should go with reconnect connect instead as disconnect may suggest the application will close? WDYT?

Also, I haven't really tested this yet, but what is your experience with dropping the connection and have it reconnect. Does ncspot recover from it nicely or is there some extra work needed?

@hrkfdn
Copy link
Owner

hrkfdn commented Feb 26, 2023

Will merge it as reconnect, hope that's okay! Thanks again!

@inemajo
Copy link
Contributor Author

inemajo commented Feb 28, 2023

Yes it's better to call it reconnect, thanks for the merge !

hrkfdn added a commit to ThomasFrans/ncspot that referenced this pull request Feb 28, 2023
…n#1057)

* commands: Adding "disconnect" command to force socket shutdown

* Rename to `reconnect`

* Add documentation to README

Related to: hrkfdn#628 hrkfdn#1033

---------

Co-authored-by: Henrik Friedrichsen <[email protected]>
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

Successfully merging this pull request may close these issues.

None yet

2 participants