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

[Feature] Configurable client-side timeouts #38

Open
gmakris-rp opened this issue Feb 22, 2023 · 0 comments
Open

[Feature] Configurable client-side timeouts #38

gmakris-rp opened this issue Feb 22, 2023 · 0 comments

Comments

@gmakris-rp
Copy link

Hello!

I am opening this issue to add a few new features that would allow for greater control over the timeouts of both opening connections and individual operations.

As it is right now opening connections inherit the default timeout value of usocket:socket-connect. We could have more flexibility if that value was configurable. Additionally, a global timeout for all commands could be added, as well as the option to make the timeouts signal an error. I noticed some commands already support it as an argument but a default value for the rest would be really useful.

I have done a thorough review of the changes that need to be made in order to support this. They are very few and sensible defaults could be set so as to not affect existing users.

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